Malicious Code Injection in embarrassed_wasp_0xrequest Package
Summary
MAL-2025-102054: Malicious code in embarrassed_wasp_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 'embarrassed_wasp_0xrequest' package is part of a broader ecosystem that includes various npm packages. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards. The vulnerability in this package allows malicious actors to exploit its functionality for nefarious purposes.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and the undermining of trust in the npm ecosystem. The malicious payload can significantly affect the integrity of the software supply chain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall embarrassed_wasp_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 removing the 'embarrassed_wasp_0xrequest' package from your project until a secure version is released. You can do this by executing: npm uninstall embarrassed_wasp_0xrequest. Additionally, monitor your package-lock.json file for any unexpected changes or dependencies.
Conclusion
The 'embarrassed_wasp_0xrequest' package poses a significant security risk due to its malicious code that modifies package metadata. It is essential for developers to take immediate action by updating or removing the package and to monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for embarrassed_wasp_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks in your project by modifying package metadata.
You should update the package to the latest patched version or remove it from your project until a secure version is available.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Check your application using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
