Malicious Code Injection in average_guanaco_z3n Package - npm Vulnerability
Summary
MAL-2025-99683: Malicious code in average_guanaco_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 average_guanaco_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names. Their primary function is to inflate developer reputation scores for token rewards, but they also pose significant security risks due to their malicious payloads.
Vulnerability Detail
The vulnerability in the average_guanaco_z3n package stems 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, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous malicious packages flooding the npm ecosystem. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall average_guanaco_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 average_guanaco_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The average_guanaco_z3n package poses a significant security risk due to its malicious code designed to manipulate package management processes. It is essential for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and monitoring for future vulnerabilities.
See every vulnerability recorded for average_guanaco_z3n →
FAQ
The average_guanaco_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
This vulnerability can compromise your application's integrity by introducing malicious code, which may lead to security breaches and unreliable package management.
If you have installed the average_guanaco_z3n package, it is crucial to uninstall it immediately and check for any other affected packages in your project.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring 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.
