Malicious Code Injection in eventual_shrimp_0xrequest Package
Summary
MAL-2025-102276: Malicious code in eventual_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 eventual_shrimp_0xrequest package is part of a series of npm packages that have been associated with 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 for token rewards. This behavior raises significant concerns about the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the eventual_shrimp_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 the npm registry. This not only compromises the security of the affected package but also pollutes the npm registry, potentially leading to further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eventual_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 prevent the installation of the eventual_shrimp_0xrequest package by using the following command: npm uninstall eventual_shrimp_0xrequest. Additionally, review your package-lock.json file to ensure that no malicious packages are included.
Conclusion
The eventual_shrimp_0xrequest package contains malicious code that poses a significant risk to projects using it. It is crucial to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for eventual_shrimp_0xrequest →
FAQ
It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The malicious code can compromise your project's integrity by modifying essential files and republishing variants that could lead to further vulnerabilities.
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.
If no patched version is available, it is advisable to remove the package from your project to mitigate any potential risks.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about security updates for the packages you use.
