Malicious Code Injection in repulsive_mongoose_z3n: A Threat to npm Packages
Summary
MAL-2025-107919: Malicious code in repulsive_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 'repulsive_mongoose_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter critical files, such as package.json, leading to potential security risks and registry pollution.
Vulnerability Detail
The vulnerability in 'repulsive_mongoose_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, which can lead to a polluted npm registry and compromise the integrity of the ecosystem. This behavior is indicative of a broader trend where malicious actors exploit npm for personal gain, posing risks to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall repulsive_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 measure, avoid using the 'repulsive_mongoose_z3n' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which utilizes package-lock.json to alert you in real-time about open-source vulnerabilities.
Conclusion
The 'repulsive_mongoose_z3n' package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to stay informed about vulnerabilities in their projects.
See every vulnerability recorded for repulsive_mongoose_z3n →
FAQ
'repulsive_mongoose_z3n' is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing untrusted code.
You should uninstall 'repulsive_mongoose_z3n' immediately and monitor your project for any further vulnerabilities.
Yes, tools like Vulert can help you monitor your project for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring a signup.
