Malicious Code Injection in opposite_locust_z3n: A Threat to npm Packages
Summary
MAL-2025-95762: Malicious code in opposite_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 'opposite_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 known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'opposite_locust_z3n' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent applications. The malicious payload can lead to unauthorized access and manipulation of project dependencies, making it critical for developers to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opposite_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 'opposite_locust_z3n' package from your project by executing the command: 'npm uninstall opposite_locust_z3n'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'opposite_locust_z3n' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for opposite_locust_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and repopulates the npm registry with harmful variants.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to unauthorized access to your project dependencies and compromise the integrity of your application.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
If an immediate update is not possible, consider removing the package as a temporary measure until a secure version is available.
