Malicious Code Injection in supposed_bee_z3n Package - npm Vulnerability
Summary
MAL-2025-96880: Malicious code in supposed_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 supposed_bee_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package's inclusion in a broader campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall supposed_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 the supposed_bee_z3n package until a fixed version is released. Additionally, you can monitor your package-lock.json file for any suspicious changes or dependencies that may have been introduced by this package.
Conclusion
The supposed_bee_z3n package contains a significant vulnerability that can compromise the integrity of applications using it. It is essential to stay informed about such vulnerabilities and take proactive steps to secure your dependencies.
See every vulnerability recorded for supposed_bee_z3n →
FAQ
The supposed_bee_z3n package is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the installation of malicious packages that modify your application's dependencies, potentially introducing security risks and instability.
If you have installed the supposed_bee_z3n package, it is crucial to remove it and update your dependencies to ensure your application is secure.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
