Malicious Code Injection in content_beaver_z3n Package - npm Vulnerability
Summary
MAL-2025-93764: Malicious code in content_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 content_beaver_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious scripts that manipulate package data. Its primary attributes include automatic publishing capabilities, which have been exploited to inflate developer reputation scores through the generation of numerous derivative packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the content_beaver_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who may unknowingly use these compromised packages. The impact of this vulnerability can lead to reputational damage for developers and increased difficulty in managing dependencies within projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall content_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, avoid using the content_beaver_z3n package until it has been confirmed to be safe. You can also monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The content_beaver_z3n package has been identified as containing malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for any similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for content_beaver_z3n →
FAQ
The content_beaver_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate publishing processes.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry with unwanted packages.
You should uninstall the content_beaver_z3n package immediately using the command npm uninstall content_beaver_z3n.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
