Malicious Code Injection in single_bee_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-108706: Malicious code in single_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 'single_bee_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'single_bee_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names to republish variants, effectively polluting the npm registry. The ramifications include potential security risks for applications using this package, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall single_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 remove the 'single_bee_z3n' package from your project by executing: 'npm uninstall single_bee_z3n'. This will prevent any malicious scripts from executing until a secure version is available.
Conclusion
The 'single_bee_z3n' package is compromised by malicious code that alters package metadata and repackages it, posing a risk to the npm ecosystem. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time vulnerability monitoring.
See every vulnerability recorded for single_bee_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it, leading to potential security risks.
You can use Vulert, which monitors vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Consider uninstalling the package as a temporary measure to mitigate risks until a secure version is available.
While specific exploits may not be publicly documented, the nature of the vulnerability poses significant risks to applications using the affected package.
Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, ensuring your applications remain secure.
