Malicious Code Injection in opposite_rodent_z3n Package: A Threat to npm Users
Summary
MAL-2025-95764: Malicious code in opposite_rodent_z3n (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 opposite_rodent_z3n 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. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on these packages.
Vulnerability Detail
The vulnerability in the opposite_rodent_z3n package originates from its association with malicious scripts designed to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opposite_rodent_z3nIf 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 measure, users can avoid using the opposite_rodent_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The opposite_rodent_z3n package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and reputation scores. Immediate action is required to remove this package and safeguard your projects. Regular monitoring and updates are essential to maintain security in the npm ecosystem.
See every vulnerability recorded for opposite_rodent_z3n →
FAQ
The opposite_rodent_z3n package is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through automated publishing.
This vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and compromising your project's security.
You should remove the opposite_rodent_z3n package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
