Malicious Code Injection in appropriate_locust_0xrequest Package
Summary
MAL-2025-99529: Malicious code in appropriate_locust_0xrequest (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 appropriate_locust_0xrequest package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability arises from malicious code embedded in the appropriate_locust_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall appropriate_locust_0xrequestIf 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 appropriate_locust_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The appropriate_locust_0xrequest package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your software.
See every vulnerability recorded for appropriate_locust_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.
The malicious code can modify your package.json file and republish variants, potentially leading to security issues in your application.
You should uninstall the package immediately and check for any updates or alternatives.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities 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 signing up.
