Malicious Code Injection in rotten_mollusk_dumbs Package
Summary
MAL-2025-108201: Malicious code in rotten_mollusk_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 rotten_mollusk_dumbs package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of these packages is compromised due to the presence of malicious scripts that manipulate package metadata and republish variants to the npm registry.
Vulnerability Detail
The vulnerability in the rotten_mollusk_dumbs package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to unauthorized access to sensitive information or unintended consequences for developers relying on the integrity of the npm ecosystem. The malicious payload is part of a broader scheme to exploit the npm registry for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rotten_mollusk_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 measure, you can avoid using the rotten_mollusk_dumbs package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The rotten_mollusk_dumbs package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with unauthorized packages. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for rotten_mollusk_dumbs →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The malicious code modifies your package.json file, potentially exposing sensitive information and polluting the npm registry with unauthorized packages.
You should uninstall the rotten_mollusk_dumbs package immediately and review your project for any other potentially malicious dependencies.
You can use Vulert, which monitors your package-lock.json file for open-source 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.
