Malicious Code Injection in supposed_bee_requirement Package
Summary
MAL-2025-96879: Malicious code in supposed_bee_requirement (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_requirement package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the supposed_bee_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The primary risk is that it pollutes the npm registry and can potentially compromise the security of applications that utilize this package, leading to unauthorized access or exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall supposed_bee_requirementIf 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 supposed_bee_requirement package from your project by executing the following command: npm uninstall supposed_bee_requirement. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The supposed_bee_requirement package contains malicious code that poses a significant security risk to applications using it. It is crucial to update or remove this package to safeguard your project. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for supposed_bee_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json file, removes private flags, and can lead to unauthorized republishing of variants, potentially compromising your application's security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
If no patched version is available, it is advisable to remove the supposed_bee_requirement package from your project and look for a secure alternative.
Yes, regularly monitor your dependencies using tools like Vulert to stay informed about vulnerabilities and ensure your packages are up to date.
