Malicious Code Injection in creepy_baboon_z3n Package
Summary
MAL-2025-101062: Malicious code in creepy_baboon_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 creepy_baboon_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the creepy_baboon_z3n package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry and compromise the security of applications relying on this package. The malicious payload is part of a broader scheme to manipulate the npm ecosystem for token rewards, 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 creepy_baboon_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, consider using alternative packages that provide similar functionality without the risk of malicious code. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The creepy_baboon_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert to maintain the security of your applications.
See every vulnerability recorded for creepy_baboon_z3n →
FAQ
The creepy_baboon_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file and can lead to the continuous republishing of variants, polluting the npm registry and potentially compromising your application's security.
You should uninstall the creepy_baboon_z3n package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
