Malicious Code Injection in remarkable_shrimp_dumbs Package
Summary
MAL-2025-107893: Malicious code in remarkable_shrimp_dumbs (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 remarkable_shrimp_dumbs 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 derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous variants of the package, often with altered names and configurations.
Vulnerability Detail
This vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to modify the package.json file. The scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may expose their applications to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall remarkable_shrimp_dumbsIf 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 avoid using the remarkable_shrimp_dumbs package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The remarkable_shrimp_dumbs package poses a significant security risk due to its association with malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for remarkable_shrimp_dumbs →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
Using this package can lead to the inclusion of compromised code in your application, potentially exposing it to security risks and instability.
You should remove the remarkable_shrimp_dumbs package from your project and check for any alternative packages that are secure.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
