Malicious Code Injection in thirsty_lemming_0xrequest Package
Summary
MAL-2025-109619: Malicious code in thirsty_lemming_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_lemming_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 automated publishing scripts. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious design of the 'thirsty_lemming_0xrequest' package, which includes scripts that alter the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes these variants, which can lead to pollution of the npm registry and exploitation of developer reputation scores. This behavior poses significant risks, including the potential for dependency confusion and the introduction of further vulnerabilities into dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall thirsty_lemming_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 temporarily prevent the package from being used in your project by removing it from your package.json and running the following command: npm uninstall thirsty_lemming_0xrequest. This will help in avoiding any potential exploitation until a more permanent solution is available.
Conclusion
The 'thirsty_lemming_0xrequest' package poses a significant threat due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for thirsty_lemming_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.
The vulnerability can lead to pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the 'thirsty_lemming_0xrequest' package immediately to mitigate any risks associated with its malicious behavior.
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 if your application is affected without requiring any signup.
