Malicious Code Injection in rita-65: A Threat to npm Ecosystem
Summary
MAL-2025-164939: Malicious code in rita-65 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The rita-65 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript libraries and applications. However, rita-65 has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in rita-65 stems from its association with the tea.xyz token reward campaign, which utilizes malicious scripts to automatically generate and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This not only affects the reputation of developers but also poses a risk to users who may inadvertently install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-65If 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. It is advisable to monitor your dependencies closely and avoid using packages that are part of suspicious campaigns.
Conclusion
The rita-65 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with harmful derivatives. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for rita-65 →
FAQ
rita-65 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.
You should uninstall the rita-65 package immediately using the command npm uninstall rita-65.
Regularly update your dependencies, use trusted packages, and monitor your project for vulnerabilities.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
