Malicious Code Injection in wild_viper_0xrequest Package
Summary
MAL-2025-110916: Malicious code in wild_viper_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 wild_viper_0xrequest package is part of the npm ecosystem, primarily used for various web development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.
Vulnerability Detail
The vulnerability arises from malicious code embedded within the wild_viper_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to clutter the npm registry. The origin of this issue is linked to a broader campaign that utilizes autopublish scripts to automate the creation of these malicious packages, posing a risk to developers relying on npm for package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wild_viper_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 avoid using the wild_viper_0xrequest package and replace it with a trusted alternative that provides similar functionality. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The wild_viper_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your software development environment.
See every vulnerability recorded for wild_viper_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of your npm registry, making it difficult to manage dependencies and potentially exposing your project to further security risks.
You should uninstall the wild_viper_0xrequest package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies using tools like npm audit, and stay informed about the packages you use by following their repositories for updates.
