Malicious Code Injection in surprised_skunk_0xrequest Package
Summary
MAL-2025-109345: Malicious code in surprised_skunk_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 surprised_skunk_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. This behavior raises concerns about the integrity of the npm registry and the potential for malicious exploitation.
Vulnerability Detail
The vulnerability in the surprised_skunk_0xrequest package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which can pollute the npm registry and compromise the security of applications relying on this package. The malicious payload can lead to unauthorized access, data breaches, and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surprised_skunk_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 surprised_skunk_0xrequest package and replace it with a trusted alternative that provides similar functionality. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The surprised_skunk_0xrequest package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with harmful variants. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for surprised_skunk_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.
You should uninstall the surprised_skunk_0xrequest package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
