Malicious Code Injection in existing_mole_z3n Package - npm Vulnerability
Summary
MAL-2025-94366: Malicious code in existing_mole_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_mole_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code among developers. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for users who rely on it.
Vulnerability Detail
The vulnerability in the existing_mole_z3n package stems from its association with a malicious campaign that generates and publishes derivative packages with randomized names. This campaign modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. The malicious payload can lead to reputation inflation for developers and may expose users to further security risks if they inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall existing_mole_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, avoid using the existing_mole_z3n package and consider replacing it with a reputable alternative. Additionally, you can use the following command to uninstall the package: npm uninstall existing_mole_z3n.
Conclusion
The existing_mole_z3n package poses significant security risks due to its malicious code injection. It is essential to remove this package from your projects and stay informed about potential vulnerabilities in your dependencies. Utilizing tools like Vulert can help you monitor your applications effectively.
See every vulnerability recorded for existing_mole_z3n →
FAQ
The existing_mole_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
Using the existing_mole_z3n package can expose your project to security risks, including the potential for malicious code execution and reputation damage.
If you have used the existing_mole_z3n package, it is recommended to uninstall it immediately and monitor your project for any unusual behavior.
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 check your application using the Vulert playground without any signup.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.
