Malicious Code Injection in troubled_flea_0xrequest Package
Summary
MAL-2025-109850: Malicious code in troubled_flea_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 troubled_flea_0xrequest package is part of the npm ecosystem, often used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through the generation of numerous fake packages.
Vulnerability Detail
The vulnerability in the troubled_flea_0xrequest package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, change 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 applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall troubled_flea_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 workaround, you can remove the troubled_flea_0xrequest package from your project by executing the following command in your terminal: npm uninstall troubled_flea_0xrequest. This will help mitigate the risks associated with the malicious code.
Conclusion
The troubled_flea_0xrequest package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package from your projects to safeguard your applications and maintain a secure development environment.
See every vulnerability recorded for troubled_flea_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the generation of fake packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on the troubled_flea_0xrequest package.
You should uninstall the troubled_flea_0xrequest package immediately to mitigate the risks associated with its malicious code.
Due to the malicious nature of the troubled_flea_0xrequest package, it is recommended to remove it entirely rather than seeking a patch.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.
