Malicious Code Injection in appalling_quail_0xrequest Package
Summary
MAL-2025-99505: Malicious code in appalling_quail_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 appalling_quail_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This functionality, while initially appearing benign, has been exploited to introduce malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's 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 these variants, polluting the npm registry and potentially impacting other developers who may unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall appalling_quail_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, consider using a different package that offers similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.
Conclusion
The appalling_quail_0xrequest package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to take immediate action to remove this package and monitor their projects for similar vulnerabilities.
See every vulnerability recorded for appalling_quail_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated package generation.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the appalling_quail_0xrequest package immediately and check your project for any other affected packages.
Yes, regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to issues in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
