Malicious Code Injection in rita-32 Package: A Threat to npm Users
Summary
MAL-2025-164903: Malicious code in rita-32 (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-32 package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate certain functionalities within projects, but it has been compromised as part of a broader malicious campaign targeting npm packages. The vulnerability stems from the package's involvement in the tea.xyz token reward scheme, which has led to the distribution of harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the rita-32 package involves the injection of malicious code that alters the package.json file. This code removes private flags, modifies version numbers, and generates random package names, ultimately leading to the automatic publication of derivative packages. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages. The malicious payload is designed to inflate developer reputation scores for token rewards, making it a significant threat to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-32If 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-32 package by using the following command to remove it from your project: npm uninstall rita-32. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The rita-32 package poses a significant security risk due to the malicious code it contains. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications in the ever-evolving landscape of open-source software.
See every vulnerability recorded for rita-32 →
FAQ
The rita-32 package is an npm package used in JavaScript applications, but it has been compromised to include malicious code.
The malicious code modifies your package.json file, potentially leading to the publication of harmful derivative packages and compromising your project's integrity.
You should uninstall the rita-32 package immediately and check for any alternative packages that can fulfill your needs.
Yes, you can use tools like 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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
