Malicious Code Injection in rita-17 Package: A Threat to npm Ecosystem
Summary
MAL-2025-164886: Malicious code in rita-17 (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-17 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the rita-17 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also can lead to security risks for applications relying on these packages. The origin of this vulnerability is linked to a broader campaign aimed at exploiting the npm registry for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-17If 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-17 package by using the following command to uninstall it: npm uninstall rita-17. Additionally, ensure that your package-lock.json file does not reference this package to avoid accidental reinstallation.
Conclusion
The rita-17 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with harmful variants. It is essential for developers to take immediate action by uninstalling this package and monitoring their applications for vulnerabilities.
See every vulnerability recorded for rita-17 →
FAQ
The rita-17 package is a JavaScript package in the npm ecosystem, associated with a token reward campaign that has been found to contain malicious code.
The vulnerability can compromise your application's integrity by modifying package metadata and introducing potentially harmful code, which may lead to security breaches.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
If you have installed rita-17, it is crucial to uninstall it immediately using the command: npm uninstall rita-17, and ensure your package-lock.json file is updated.
Currently, there are no known patches for the rita-17 package. The best course of action is to remove the package entirely from your project.
