Malicious Code Injection in thirsty_echidna_0xrequest Package
Summary
MAL-2025-109614: Malicious code in thirsty_echidna_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_echidna_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automatically publish derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability in the 'thirsty_echidna_0xrequest' package stems from malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion attacks and the inflation of developer reputation scores through illegitimate means.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall thirsty_echidna_0xrequest
If 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 remove the 'thirsty_echidna_0xrequest' package from your project by executing:
npm uninstall thirsty_echidna_0xrequest
This will prevent the malicious code from executing in your application.
Conclusion
The 'thirsty_echidna_0xrequest' package contains malicious code that poses significant security risks. It is crucial to monitor for vulnerabilities, update packages regularly, and consider using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for thirsty_echidna_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages.
The malicious code modifies package.json files and can lead to security vulnerabilities, including dependency confusion.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
If no patched version is available, consider removing the package from your project until a secure version is released.