Malicious Code Injection in elderly_mollusk_replicate_automation Package
Summary
MAL-2025-101998: Malicious code in elderly_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 elderly_mollusk_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which exploits npm's publishing mechanisms.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall elderly_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 avoid using the elderly_mollusk_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The elderly_mollusk_replicate_automation package poses significant risks due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for elderly_mollusk_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been identified as malicious.
It can compromise your project's integrity by introducing malicious code and inflating npm registry pollution.
You should remove the package immediately and check for any affected dependencies.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.
