Malicious Code Injection in rita-41: A Threat to npm Users
Summary
MAL-2025-164913: Malicious code in rita-41 (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
rita-41 is an npm package that is part of the tea.xyz token reward campaign, which has been identified as a source of malicious activity. This package is designed to interact with the npm registry, and its primary function is to facilitate the generation and publication of derivative packages. However, it has been compromised to include scripts that manipulate package metadata and flood the registry with unwanted variants, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in rita-41 originates from its association with a malicious campaign that employs autopublish scripts to alter package.json files. This manipulation removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include the pollution of the npm registry, potential security risks for applications relying on these packages, and the inflation of developer reputation scores through unethical means.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-41If 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
If an immediate update is not feasible, consider removing the rita-41 package from your project to prevent any potential exploitation. You can do this by executing: 'npm uninstall rita-41'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The rita-41 package poses a significant risk due to its malicious code injection vulnerability. Users are advised to update or remove the package to safeguard their applications. Continuous monitoring and proactive management of dependencies are essential to maintain security.
See every vulnerability recorded for rita-41 →
FAQ
rita-41 is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce malicious code into your application, compromising its security.
You should uninstall the rita-41 package immediately and check for any unauthorized changes in your project.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
