Malicious Code Injection in rita-71: A Threat to npm Users
Summary
MAL-2025-164946: Malicious code in rita-71 (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-71 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. This package, like many others in the campaign, is vulnerable to malicious exploitation due to its autopublish scripts that can modify package metadata and republish variants, leading to potential abuse in the npm registry.
Vulnerability Detail
The vulnerability in rita-71 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing them to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-71If 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-71 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly audited for any unauthorized changes.
Conclusion
The rita-71 package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for rita-71 →
FAQ
Rita-71 is an npm package that is part of a campaign to generate and publish derivative packages, often for the purpose of inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your project to security risks and making it difficult to trust the integrity of your dependencies.
You should uninstall the rita-71 package immediately using the command: npm uninstall rita-71, and consider using alternative packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
