Malicious Code Injection in general_warbler_0xrequest Package
Summary
MAL-2025-103079: Malicious code in general_warbler_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 general_warbler_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been linked to the tea.xyz token reward campaign, notorious for flooding npm with malicious packages. Its primary function is to facilitate token rewards but has been exploited to generate and publish derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the general_warbler_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices. The ramifications include potential pollution of the npm registry and compromise of developer environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall general_warbler_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 remove the general_warbler_0xrequest package from your project by executing: npm uninstall general_warbler_0xrequest. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The general_warbler_0xrequest package poses a significant risk due to its malicious code that alters essential project files and can lead to broader issues within the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for general_warbler_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token rewards but has been found to contain malicious code.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry with unwanted packages.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
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.
