Malicious Code Injection in glorious_bee_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-103286: Malicious code in glorious_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package glorious_bee_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, notorious for flooding npm with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous derivative packages with altered names and versions.
Vulnerability Detail
The vulnerability in glorious_bee_z3n originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The malicious payload can also affect the reputation of developers and the overall trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall glorious_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 use the following command to prevent the installation of malicious packages: 'npm config set save-exact true'. This will ensure that only the exact version of packages is installed, reducing the risk of inadvertently including malicious variants.
Conclusion
The glorious_bee_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputations. It is crucial to remove this package from your projects and monitor for similar vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for glorious_bee_z3n →
FAQ
glorious_bee_z3n is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the glorious_bee_z3n package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure that you only install packages from trusted sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
