Malicious Code Injection in impressed_locust_z3n: A Threat to npm Packages
Summary
MAL-2025-104018: Malicious code in impressed_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 'impressed_locust_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package is designed to automate the publication of derivative packages, potentially leading to a polluted npm registry.
Vulnerability Detail
The vulnerability in 'impressed_locust_z3n' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is intended to create numerous derivative packages that can clutter the npm registry and mislead developers. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which incentivizes such malicious practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall impressed_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 remove the 'impressed_locust_z3n' package from your project by executing: 'npm uninstall impressed_locust_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'impressed_locust_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.
See every vulnerability recorded for impressed_locust_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json and publishes numerous derivative packages to inflate reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further vulnerabilities.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they affect your application.
If an immediate update is not possible, consider uninstalling the package and monitoring your application for any unusual behavior.
