Malicious Code Injection in rita-82 Package: A Threat to npm Users
Summary
MAL-2025-164958: Malicious code in rita-82 (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-82 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The primary functionality of rita-82 is to facilitate the automatic generation and publication of derivative packages. However, its vulnerability lies in its ability to execute harmful scripts that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the rita-82 package originates from its design to include autopublish scripts that 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. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for users to identify legitimate packages. The malicious payload poses significant risks, including the potential for unauthorized access to sensitive data and the spread of further malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-82If 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 workaround, you can temporarily avoid using the rita-82 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file for any vulnerabilities using tools like Vulert.
Conclusion
The rita-82 package poses a significant threat due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove this package from their projects to safeguard their applications. Utilizing tools like Vulert can help in monitoring for vulnerabilities and ensuring the integrity of your software.
See every vulnerability recorded for rita-82 →
FAQ
The rita-82 package is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the modification of your package.json file, unauthorized access to sensitive data, and the pollution of the npm registry with malicious packages.
You should uninstall the rita-82 package immediately and check for any dependencies that may rely on it. Consider replacing it with secure alternatives.
You can use tools like Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to access the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
