Malicious Code Injection in rita-22 Package: npm Vulnerability Overview
Summary
MAL-2025-164892: Malicious code in rita-22 (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-22 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores. This package has been identified as malicious due to its ability to modify package metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in the rita-22 package originates from its malicious code, which includes autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also allows the package to modify the package.json file by removing private flags and changing version numbers. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-22
If 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 rita-22 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The rita-22 package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. It is crucial to remove this package from your project and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for rita-22 →
FAQ
The rita-22 package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the modification of your package.json file and the introduction of malicious code, which may compromise your project's security.
You should uninstall the rita-22 package immediately using 'npm uninstall rita-22' and monitor your project for any further vulnerabilities.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review package sources before installation.