Malicious Code Injection in rita-3 Package: A Threat to npm Ecosystem
Summary
MAL-2025-164900: Malicious code in rita-3 (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 rita-3 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate various functionalities within applications, but it has recently been implicated in a malicious campaign. This campaign involves the automatic generation and publication of derivative packages with the intent to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm packages.
Vulnerability Detail
The vulnerability in the rita-3 package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential security risks for applications that depend on these packages. The origin of this vulnerability is linked to the malicious intent behind the package's creation, which aims to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-3If 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 remove the rita-3 package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall rita-3'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The rita-3 package poses a significant security risk due to its malicious code injection vulnerability. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for rita-3 →
FAQ
The rita-3 package is a JavaScript package available on npm, primarily used for various functionalities in applications. However, it has been identified as part of a malicious campaign.
The vulnerability can lead to the injection of malicious code, which may compromise the integrity of your application and expose it to security risks.
If you are using rita-3, it is recommended to update the package to the latest version or remove it from your project until a secure version is available.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
