Malicious Code Injection in level_bee_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95234: Malicious code in level_bee_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 level_bee_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in level_bee_z3n originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags and changing version numbers. The scripts generate random package names, primarily themed around Indonesian culture, and continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall level_bee_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 avoid using level_bee_z3n and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The level_bee_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for level_bee_z3n →
FAQ
level_bee_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that depend on this package.
You should uninstall the package immediately using 'npm uninstall level_bee_z3n' and monitor your project for any further vulnerabilities.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
