Malicious Code Vulnerability in wee_rabbit_z3n Package
Summary
MAL-2025-92183: Malicious code in wee_rabbit_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 wee_rabbit_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It has been identified as part of a campaign that exploits npm's publishing features to inflate developer reputation scores through the creation of numerous derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry for malicious purposes.
Vulnerability Detail
The vulnerability originates from the package being involved in the tea.xyz token reward campaign, which floods npm with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior can pollute the npm registry and compromise the integrity of the ecosystem, potentially affecting other developers and applications relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wee_rabbit_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 workaround, you can avoid using the wee_rabbit_z3n package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The wee_rabbit_z3n package is compromised by malicious code that can affect the npm ecosystem. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help keep your dependencies secure and alert you to potential vulnerabilities.
See every vulnerability recorded for wee_rabbit_z3n →
FAQ
wee_rabbit_z3n 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 pollution of the npm registry, potentially affecting the integrity of your application and other dependencies.
You should remove the wee_rabbit_z3n package from your project and monitor for any updates or patches.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
