Malicious Code Exploit in ridiculous_locust_0xrequest Package
Summary
MAL-2025-108067: Malicious code in ridiculous_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 ridiculous_locust_0xrequest package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign. It contains scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This leads to the continuous republishing of variants, which can pollute the npm registry and compromise the security of dependent projects. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ridiculous_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 ridiculous_locust_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.
Conclusion
The ridiculous_locust_0xrequest package poses a significant security risk due to its malicious code designed to manipulate package metadata and publish unauthorized variants. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities.
See every vulnerability recorded for ridiculous_locust_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to unauthorized access to sensitive information and disrupt the normal functioning of your application.
You should uninstall the package immediately and look for alternatives. Use 'npm uninstall ridiculous_locust_0xrequest' to remove it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.
