Malicious Code Injection in citra-kue55-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-100529: Malicious code in citra-kue55-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'citra-kue55-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in 'citra-kue55-ruro' originates from its association with a malicious campaign that employs scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall citra-kue55-ruroIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the 'citra-kue55-ruro' package altogether. If it is already in use, consider replacing it with a similar package that does not have known vulnerabilities. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The 'citra-kue55-ruro' package poses a significant security risk due to its malicious code that alters its metadata and repackages itself. Users are advised to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your software dependencies.
See every vulnerability recorded for citra-kue55-ruro →
FAQ
The main issue is that it contains malicious code that modifies its own metadata and repackages itself, potentially leading to security risks.
You can use Vulert to check your package-lock.json file for vulnerabilities without needing to install any software.
You should remove the package from your project and replace it with a secure alternative.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time by analyzing your package-lock.json.
Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.
