Malicious Code Injection in close_beaver_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-100604: Malicious code in close_beaver_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 close_beaver_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 deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the close_beaver_z3n package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to security breaches and compromised applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall close_beaver_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 close_beaver_z3n package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package-lock.json file for any unauthorized changes.
Conclusion
The close_beaver_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By removing this package and using tools like Vulert, developers can protect their applications from potential threats.
See every vulnerability recorded for close_beaver_z3n →
FAQ
The close_beaver_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application uses the close_beaver_z3n package, it may be at risk of being compromised due to the malicious scripts that alter package configurations and publish harmful variants.
You should immediately uninstall the close_beaver_z3n package using the command npm uninstall close_beaver_z3n and review your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
