Malicious Code Injection in prepared_bee_z3n Package
Summary
MAL-2025-95988: Malicious code in prepared_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 prepared_bee_z3n package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks for applications relying on it.
Vulnerability Detail
The vulnerability in the prepared_bee_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate and publish numerous derivative packages with randomized names, thereby polluting the npm registry. The malicious payload can compromise the integrity of applications using this package, potentially leading to unauthorized access or data manipulation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prepared_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 measure, you can avoid using the prepared_bee_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly reviewed for any unauthorized changes.
Conclusion
The prepared_bee_z3n package poses a significant security risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for any unauthorized changes to your dependencies.
See every vulnerability recorded for prepared_bee_z3n →
FAQ
The prepared_bee_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.
You should immediately uninstall the prepared_bee_z3n package and review your package.json file for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your 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.
