Malicious Code Injection in atomic_monkey_z3n: A Threat to npm Packages
Summary
MAL-2025-93299: Malicious code in atomic_monkey_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 atomic_monkey_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 distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, potentially harming developers and users by polluting the npm registry with harmful packages.
Vulnerability Detail
The vulnerability in atomic_monkey_z3n stems from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to a polluted npm registry. This can result in developers unknowingly using compromised packages, which may contain harmful code or lead to security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall atomic_monkey_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, you can avoid using the atomic_monkey_z3n package and any packages that depend on it. Additionally, consider using a package-lock.json file to lock dependencies to known safe versions.
Conclusion
The atomic_monkey_z3n package poses a significant risk due to its malicious code that can compromise the integrity of npm packages. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for atomic_monkey_z3n →
FAQ
atomic_monkey_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with harmful packages.
If your project uses atomic_monkey_z3n, it may inadvertently include malicious code that can compromise the security of your application and its users.
You should immediately remove the atomic_monkey_z3n package from your project and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
