Malicious Code Injection in existing_rabbit_z3n Package
Summary
MAL-2025-94368: Malicious code in existing_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 existing_rabbit_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to a polluted npm registry.
Vulnerability Detail
The vulnerability in the existing_rabbit_z3n package arises from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished. The origin of this vulnerability is linked to a campaign that floods the npm registry with such packages, potentially leading to reputation damage for developers and security risks for users who unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall existing_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 temporary workaround, you can avoid using the existing_rabbit_z3n package and replace it with a trusted alternative. Always verify the integrity and source of the packages you intend to use in your project.
Conclusion
The existing_rabbit_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By following the recommended steps to uninstall the package and using tools like Vulert, developers can protect their projects from potential threats.
See every vulnerability recorded for existing_rabbit_z3n →
FAQ
The existing_rabbit_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code modifies your package.json file, which can lead to the installation of untrusted packages and potential security vulnerabilities in your project.
If you have installed the existing_rabbit_z3n package, you should immediately uninstall it using the command 'npm uninstall existing_rabbit_z3n' and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Yes, there are many trusted alternatives available in the npm registry. Always ensure to review the package's documentation and community feedback before integrating it into your project.
