Malicious Code Injection in annoyed_bug_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-99471: Malicious code in annoyed_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
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 'annoyed_bug_z3n' package is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's publishing system, generating numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this comes at the cost of integrity and security within the npm registry.
Vulnerability Detail
The vulnerability in the 'annoyed_bug_z3n' package stems from its malicious payload, 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, effectively polluting the npm registry. The origin of this issue is linked to automated scripts that are part of the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms for malicious purposes. The ramifications include potential security risks for developers and users relying on the integrity of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall annoyed_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, you can remove the 'annoyed_bug_z3n' package from your project by executing the command: 'npm uninstall annoyed_bug_z3n'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. Vulert can analyze your package-lock.json file to alert you in real-time about any open-source vulnerabilities.
Conclusion
The 'annoyed_bug_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at exploiting the publishing system for token rewards. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert for ongoing monitoring.
See every vulnerability recorded for annoyed_bug_z3n →
FAQ
The 'annoyed_bug_z3n' package is part of a malicious campaign that aims to exploit npm's publishing system for token rewards.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should uninstall the 'annoyed_bug_z3n' package and check for any updates or patches available for your dependencies.
Yes, Vulert can monitor your package-lock.json file for vulnerabilities and alert you in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
