Malicious Code Injection in human_bee_z3n Package - npm Vulnerability
Summary
MAL-2025-98756: Malicious code in human_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 human_bee_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a target for malicious activities.
Vulnerability Detail
The vulnerability in the human_bee_z3n package stems from its inclusion in a malicious campaign that 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 these variants, polluting the npm registry and potentially compromising the integrity of dependent applications. The malicious payload can affect any application that relies on this package, leading to unauthorized access or manipulation of application data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall human_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 human_bee_z3n package and replace it with a trusted alternative. Ensure to audit your package-lock.json file for any other potentially vulnerable packages.
Conclusion
The human_bee_z3n package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and regularly audit your dependencies to maintain the security of your applications.
See every vulnerability recorded for human_bee_z3n →
FAQ
The human_bee_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm registry.
The vulnerability can lead to unauthorized modifications of your application's package.json file, potentially compromising your application's integrity and security.
If you have installed the human_bee_z3n package, you should uninstall it immediately using npm uninstall human_bee_z3n and audit your dependencies for other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, you should look for trusted and well-maintained alternatives that provide similar functionality without the associated risks.
