Malicious Code Injection in wee_guppy_0xrequest: npm Package Vulnerability
Summary
MAL-2025-110785: Malicious code in wee_guppy_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 'wee_guppy_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised, leading to significant security concerns. The vulnerability allows for the automatic generation and publication of derivative packages, which can manipulate developer reputation scores.
Vulnerability Detail
The vulnerability in 'wee_guppy_0xrequest' originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks 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 wee_guppy_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 'wee_guppy_0xrequest' package from your project by executing: 'npm uninstall wee_guppy_0xrequest'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'wee_guppy_0xrequest' package has been identified as having a serious vulnerability due to malicious code that affects the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for wee_guppy_0xrequest →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with compromised packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Using the compromised package can lead to the pollution of the npm registry and may expose your project to further security risks.
Check the npm registry for any updated versions of the package that may contain security patches.
As a temporary measure, uninstall the package using 'npm uninstall wee_guppy_0xrequest' to mitigate risks until a secure version is released.
