Malicious Code Injection in common_mongoose_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93651: Malicious code in common_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 package 'common_mongoose_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'common_mongoose_z3n' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall common_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 'common_mongoose_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'common_mongoose_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. Developers must take immediate action to remove this package and ensure their projects are secure by using trusted alternatives and monitoring for vulnerabilities.
See every vulnerability recorded for common_mongoose_z3n →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed 'common_mongoose_z3n', you should uninstall it immediately using 'npm uninstall common_mongoose_z3n' and review your dependencies for any other malicious packages.
While specific exploits have not been detailed, the manipulation of the npm registry can lead to broader security issues for developers using affected packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
