Malicious Code Vulnerability in striking_shrew_0xrequest Package
Summary
MAL-2025-109194: Malicious code in striking_shrew_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 striking_shrew_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package is particularly vulnerable due to its association with scripts that automatically publish variants to the npm registry, leading to potential abuse.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the striking_shrew_0xrequest package, which is linked to the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall striking_shrew_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 workaround, you can temporarily avoid using the striking_shrew_0xrequest package by replacing it with a similar, trusted package from the npm registry. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The striking_shrew_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for striking_shrew_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and exposing your project to potential security risks.
You should remove the striking_shrew_0xrequest package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
