Malicious Code Injection in rita-50 Package: A Threat to npm Users
Summary
MAL-2025-164923: Malicious code in rita-50 (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-50 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate various functionalities within the npm environment. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the rita-50 package stems from its inclusion in a malicious campaign that utilizes scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices. The ramifications include the pollution of the npm registry and potential security risks for users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-50If 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-50 package altogether. If it is already installed, you can uninstall it using the command: npm uninstall rita-50. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The rita-50 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Users are advised to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your software.
See every vulnerability recorded for rita-50 →
FAQ
The rita-50 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign, which has been identified as malicious.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the rita-50 package immediately and monitor your project for any vulnerabilities using tools like Vulert.
Currently, there is no specific patch for the rita-50 package. It is advisable to remove the package from your project.
Vulert monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file, ensuring your project remains secure.
