Malicious Code Injection in content_beetle_z3n Package
Summary
MAL-2025-100913: Malicious code in content_beetle_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_beetle_z3n package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the content_beetle_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall content_beetle_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 remove the content_beetle_z3n package from your project by executing: npm uninstall content_beetle_z3n. This will prevent any malicious code from executing until a patched version is available.
Conclusion
The content_beetle_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to stay vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for content_beetle_z3n →
FAQ
The content_beetle_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed the content_beetle_z3n package, you should uninstall it immediately and monitor your application for any unusual behavior.
Yes, you can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
