Malicious Code Injection in regular_ape_z3n Package - npm Vulnerability
Summary
MAL-2025-107821: Malicious code in regular_ape_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 regular_ape_z3n package 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 and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the regular_ape_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is executed through autopublish scripts that continuously republish variants of the package, thereby polluting the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security risks and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall regular_ape_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 workaround, you can avoid using the regular_ape_z3n package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The regular_ape_z3n package poses a significant risk due to its malicious behavior aimed at polluting the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for regular_ape_z3n →
FAQ
The regular_ape_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.
If you have installed the regular_ape_z3n package, it is advisable to remove it from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your open-source dependencies without requiring access to your code.
