Malicious Code Injection in tasty_shrimp-strongdev Package
Summary
MAL-2025-109518: Malicious code in tasty_shrimp-strongdev (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 tasty_shrimp-strongdev package is part of the npm ecosystem, often used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. 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 proliferation of malicious packages in the npm registry, potentially compromising the integrity of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tasty_shrimp-strongdevIf 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 avoid using the tasty_shrimp-strongdev package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The tasty_shrimp-strongdev package poses a significant security risk due to its malicious code designed to manipulate npm registry behavior. It is crucial to remove this package and monitor your dependencies for any vulnerabilities to maintain application security.
See every vulnerability recorded for tasty_shrimp-strongdev →
FAQ
The impact includes potential exposure to malicious code that can compromise application integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Remove the package from your project and check for any dependencies that may have been affected by it.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities without requiring code access.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
