Malicious Code Vulnerability in disappointed_louse_0xrequest Package
Summary
MAL-2025-101615: Malicious code in disappointed_louse_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 disappointed_louse_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the disappointed_louse_0xrequest package, which contains scripts that automatically modify the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem, potentially affecting other packages and developers who depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall disappointed_louse_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 disappointed_louse_0xrequest package and replace it with a trusted alternative that provides similar functionality without the risk of malicious behavior.
Conclusion
The disappointed_louse_0xrequest package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. Developers should take immediate action to remove this package and monitor their projects for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for disappointed_louse_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting other developers.
You should uninstall the package immediately and check your package-lock.json file for any lingering references to it.
Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
