Malicious Code Injection in relaxed_beaver_z3n: npm Package Vulnerability
Summary
MAL-2025-96263: Malicious code in relaxed_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 'relaxed_beaver_z3n' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry 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 potential security risks for users.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the 'relaxed_beaver_z3n' package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly integrate these malicious packages into their projects. The autopublish scripts included in this package are designed to continuously republish variants, further exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall relaxed_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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor and control your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'relaxed_beaver_z3n' package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for relaxed_beaver_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and stability.
You should remove the 'relaxed_beaver_z3n' package from your project and monitor for any updates or patches.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json, providing real-time insights into potential risks.
