Malicious Code Injection in Thorough Mollusk Replicate Automation Package
Summary
MAL-2025-109631: Malicious code in thorough_mollusk_replicate_automation (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 'thorough_mollusk_replicate_automation' package is part of the npm ecosystem, typically utilized for automation tasks. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is linked to the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'thorough_mollusk_replicate_automation' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which pollutes the npm registry and can lead to significant security risks, including the potential for dependency confusion and exploitation of unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall thorough_mollusk_replicate_automationIf 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 remove the 'thorough_mollusk_replicate_automation' package from your project by executing: 'npm uninstall thorough_mollusk_replicate_automation'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'thorough_mollusk_replicate_automation' package has been compromised with malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for thorough_mollusk_replicate_automation →
FAQ
The malicious code modifies the package.json file to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check if your application is affected.
Using this package can lead to dependency confusion, reputation damage, and potential exploitation by malicious actors.
Regularly auditing your dependencies and using tools like Vulert can help identify vulnerabilities early and mitigate risks.
If an immediate update is not possible, consider removing the package from your project until a secure version is released.
