Malicious Code Injection in rita-92: A Threat to npm Ecosystem
Summary
MAL-2025-164969: Malicious code in rita-92 (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-92 package 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 known to flood the npm registry with malicious packages. The primary function of rita-92 is to facilitate the distribution of software, but its recent compromise has raised significant security concerns.
Vulnerability Detail
The vulnerability in rita-92 originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The package contains scripts designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-92If 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 prevent the installation of the rita-92 package by using the following command: npm uninstall rita-92. Additionally, ensure that your package.json file does not include any references to this package.
Conclusion
The rita-92 package has been compromised, posing significant risks to users and the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help safeguard your applications from such threats.
See every vulnerability recorded for rita-92 →
FAQ
The vulnerability involves malicious code that modifies package.json files and repackages the software with random names, leading to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Using the rita-92 package can lead to security breaches, as it may introduce malicious code into your application and affect the integrity of the npm registry.
Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using packages from untrusted sources to minimize risks.
If you cannot update or remove the package, consider isolating it in a separate environment and closely monitor its behavior to mitigate potential risks.
