Malicious Code Injection in tender_shrimp_0xrequest Package
Summary
MAL-2025-109543: Malicious code in tender_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 tender_shrimp_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this package has been identified as malicious, containing scripts that manipulate package metadata and republish variants to clutter the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious nature of the tender_shrimp_0xrequest package, which includes 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 compromising their projects with untrusted code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tender_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 measure, you can avoid using the tender_shrimp_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall tender_shrimp_0xrequest.
Conclusion
The tender_shrimp_0xrequest package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with untrusted packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for tender_shrimp_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce untrusted code into your project, compromising its integrity.
You should uninstall the tender_shrimp_0xrequest package immediately and check for any alternative packages that are safe to use.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies using tools like npm audit, and consider using services like Vulert to monitor for vulnerabilities in real-time.
