Malicious Code Injection in willing_mongoose_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-110936: Malicious code in willing_mongoose_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 'willing_mongoose_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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'willing_mongoose_z3n' originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This can lead to a compromised development environment, where developers may unknowingly use these malicious packages, potentially exposing their applications to further vulnerabilities and attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall willing_mongoose_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 'willing_mongoose_z3n' package and any other packages that are part of the malicious campaign. Additionally, consider using tools like Vulert to monitor your package dependencies 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 'willing_mongoose_z3n' package poses a significant risk to developers using npm. It is crucial to remove this package and any associated malicious packages from your projects to maintain a secure development environment. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your dependencies.
See every vulnerability recorded for willing_mongoose_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
If you have this package installed, it may compromise your development environment and expose your application to further vulnerabilities.
You should uninstall the package immediately and check for any other malicious packages in your project.
Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
