Malicious Code Injection in ashamed_coyote_0xrequest Package
Summary
MAL-2025-99626: Malicious code in ashamed_coyote_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 'ashamed_coyote_0xrequest' package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign aimed at exploiting npm's package management system. This package is linked to the tea.xyz token reward scheme, which has been known to flood the npm registry with derivative packages that can harm developers' reputations and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the 'ashamed_coyote_0xrequest' package stems from its 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 not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ashamed_coyote_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 workaround, you can avoid using the 'ashamed_coyote_0xrequest' package altogether. If it is already in your project, you can run the following command to uninstall it: npm uninstall ashamed_coyote_0xrequest.
Conclusion
The 'ashamed_coyote_0xrequest' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for ashamed_coyote_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using this package can compromise your project's integrity and expose it to malicious activities, including reputation damage.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
You should uninstall the package immediately and monitor your project for any unusual behavior.