Malicious Code Injection in curly_marmot_replicate_automation Package
Summary
MAL-2025-101158: Malicious code in curly_marmot_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 curly_marmot_replicate_automation package is part of the npm ecosystem, often used for automation tasks in JavaScript applications. 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 the npm registry by generating and publishing numerous variants of itself, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign linked to the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and create random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall curly_marmot_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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities in real-time.
Conclusion
The curly_marmot_replicate_automation package poses a significant risk due to its malicious nature, which can compromise the integrity of your projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for curly_marmot_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been identified as malicious.
It can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
Remove the package from your project and monitor for any updates or patches.
Yes, you can use the Vulert playground to analyze your package-lock.json file for vulnerabilities without needing to sign up.
Vulert monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file, providing real-time insights.
