Malicious Code Injection in serious_shrimp_0xrequest Package
Summary
MAL-2025-108565: Malicious code in serious_shrimp_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 serious_shrimp_0xrequest package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which incentivizes the creation of derivative packages that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the serious_shrimp_0xrequest package stems from its malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, ultimately leading to the pollution of the npm registry. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms to inflate developer reputation scores for token rewards, posing significant risks to developers and users relying on the integrity of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall serious_shrimp_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 serious_shrimp_0xrequest package from your project by executing the following command: npm uninstall serious_shrimp_0xrequest. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The serious_shrimp_0xrequest package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring for updates to safeguard their projects.
See every vulnerability recorded for serious_shrimp_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the injection of malicious code, compromising the integrity of your project and potentially affecting other dependencies.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
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.
Vulert is a tool that uses package-lock.json to monitor open-source vulnerabilities in your software, providing alerts in real-time.
