Malicious Code Injection in average_locust_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-99684: Malicious code in average_locust_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 average_locust_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code among developers. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in average_locust_z3n originates from its association with the tea.xyz token reward campaign. This campaign utilizes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The ramifications include compromised developer reputation scores and the risk of integrating malicious code into legitimate applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall average_locust_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_locust_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The average_locust_z3n package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to be vigilant and remove any affected packages from their projects to maintain security and integrity. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for average_locust_z3n →
FAQ
average_locust_z3n is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with derivative packages.
Using the average_locust_z3n package can lead to the integration of malicious code into your project, compromising its security and potentially affecting your application's performance.
If you have installed average_locust_z3n, you should uninstall it immediately using the command npm uninstall average_locust_z3n and look for alternative packages.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities without requiring access to the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
