Malicious Code Injection in rita-4: A Threat to npm Ecosystem
Summary
MAL-2025-164911: Malicious code in rita-4 (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-4 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate various functionalities within applications that rely on JavaScript libraries. However, rita-4 has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to severe security risks for developers and users alike.
Vulnerability Detail
The vulnerability in rita-4 stems from its association with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior not only pollutes the npm registry but also poses risks of dependency confusion and potential code execution vulnerabilities in applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rita-4If 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-4 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The rita-4 package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. Developers are advised to uninstall the package and monitor their applications for any potential vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.
See every vulnerability recorded for rita-4 →
FAQ
rita-4 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can lead to dependency confusion, unauthorized code execution, and potential security breaches in applications that depend on the compromised package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check your application without any signup.
You should uninstall the rita-4 package immediately using the command npm uninstall rita-4 and look for alternative packages.
Currently, there is no patch available for rita-4. It is recommended to remove the package until a secure version is released.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
