Malicious Code Injection in massive_beaver_z3n: A Threat to npm Users
Summary
MAL-2025-88318: Malicious code in massive_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 package 'massive_beaver_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate the npm ecosystem for fraudulent purposes, such as inflating developer reputation scores.
Vulnerability Detail
The vulnerability in 'massive_beaver_z3n' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall massive_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 'massive_beaver_z3n' package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The 'massive_beaver_z3n' package poses a significant threat to npm users due to its malicious behavior. It is crucial to remove this package from your projects and stay vigilant about the security of your dependencies. Utilizing tools like Vulert can help you monitor and manage vulnerabilities effectively.
See every vulnerability recorded for massive_beaver_z3n →
FAQ
It is an npm package that has been identified as malicious, associated with fraudulent activities in the npm ecosystem.
Using this package can lead to unauthorized modifications in your project, potentially compromising your application's integrity and security.
You should uninstall the package immediately and review your project for any other dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
