Malicious Code Injection in npm Package 'thirsty_loon_0xrequest'
Summary
MAL-2025-109620: Malicious code in thirsty_loon_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 'thirsty_loon_0xrequest' package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'thirsty_loon_0xrequest' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall thirsty_loon_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 'thirsty_loon_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks. Always validate the integrity of the packages you use by checking their source and reputation.
Conclusion
The 'thirsty_loon_0xrequest' package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial to remove this package from your project and monitor your dependencies for similar vulnerabilities to ensure the integrity and security of your applications.
See every vulnerability recorded for thirsty_loon_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of your application if it relies on this or similar malicious packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately and review your other dependencies for similar vulnerabilities.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities using just your package-lock.json file.
