Malicious Code Injection in rita-39 Package: A Threat to npm Users
Summary
MAL-2025-164910: Malicious code in rita-39 (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-39 package is part of the npm ecosystem, often utilized in various JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically contain scripts that manipulate package metadata and publish derivative packages, posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability in the rita-39 package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to the pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages on npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-39If 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-39 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The rita-39 package poses a significant risk due to its malicious code that alters package metadata and publishes harmful derivatives. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for rita-39 →
FAQ
The rita-39 package is an npm package that has been linked to malicious activities, specifically related to the tea.xyz token reward campaign.
The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising your project's integrity and security.
You should remove the rita-39 package from your project immediately and consider using alternative packages.
You can use Vulert to monitor your project's dependencies for vulnerabilities. It analyzes your package-lock.json file to provide real-time alerts.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring 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.
