Malicious Code Injection in anonymous_bug_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93236: Malicious code in anonymous_bug_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 'anonymous_bug_z3n' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'anonymous_bug_z3n' stems from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly depend on these tainted packages, leading to potential security breaches and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall anonymous_bug_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, consider using a package manager that allows you to lock down your dependencies to specific versions, preventing the installation of malicious packages. You can also monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'anonymous_bug_z3n' package represents a significant threat within the npm ecosystem due to its malicious behavior of altering package files and republishing variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential security risks.
See every vulnerability recorded for anonymous_bug_z3n →
FAQ
The main risk is that it modifies your package.json file and repopulates the npm registry with malicious variants, potentially leading to security vulnerabilities in your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without any installation.
No, there is no patch available for this package as it is inherently malicious. The best course of action is to remove it from your project.
If you have installed the anonymous_bug_z3n package, you should immediately uninstall it using 'npm uninstall anonymous_bug_z3n' and review your project for any other potentially malicious packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and be cautious when adding new packages from unverified sources.
