Malicious Code Vulnerability in upset_shark_0xrequest Package
Summary
MAL-2025-110216: Malicious code in upset_shark_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 upset_shark_0xrequest package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is associated with the tea.xyz token reward scheme, which has been flooding the npm registry with derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in the package are designed to automate these actions, making it difficult for developers to maintain clean and secure environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall upset_shark_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 upset_shark_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package dependencies for any updates or vulnerabilities.
Conclusion
The upset_shark_0xrequest package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and your application. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for upset_shark_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application's dependencies.
You should uninstall the package immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.
