Malicious Code Injection in popular_wombat_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95941: Malicious code in popular_wombat_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 'popular_wombat_z3n' is part of a series of npm packages that have been identified as malicious. These packages are linked to a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the 'popular_wombat_z3n' package, which is designed to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a significant pollution of the npm registry, potentially affecting other developers and projects relying on npm packages. The ramifications include compromised project integrity and increased difficulty in managing dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall popular_wombat_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 manually remove the package from your project by executing the command: npm uninstall popular_wombat_z3n. Additionally, consider using a package-lock.json file to monitor your dependencies and ensure that no malicious packages are introduced.
Conclusion
The 'popular_wombat_z3n' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and republish behavior. It is crucial for developers to remove this package and monitor their dependencies to maintain project integrity.
See every vulnerability recorded for popular_wombat_z3n →
FAQ
It is an npm package identified as malicious, designed to manipulate package metadata and republish itself under various names.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the package immediately using the command: npm uninstall popular_wombat_z3n.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
