Malicious Code Injection in comparative_sloth_replicate_automation Package
Summary
MAL-2025-100748: Malicious code in comparative_sloth_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 comparative_sloth_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks related to comparative analysis. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to pollution of the npm registry and can compromise the integrity of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comparative_sloth_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 comparative_sloth_replicate_automation package until a secure version is released. Additionally, you can monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities.
Conclusion
The comparative_sloth_replicate_automation package is compromised with malicious code that can affect the integrity of applications. It is crucial to update or remove the package to safeguard your project. Utilizing tools like Vulert can help monitor and alert you about vulnerabilities in real-time.
See every vulnerability recorded for comparative_sloth_replicate_automation →
FAQ
It is an npm package used for automation tasks related to comparative analysis but has been compromised with malicious code.
The vulnerability can lead to the pollution of the npm registry and potentially compromise the integrity of your application if it relies on this package.
You should update the package to a patched version if available or remove it from your project to mitigate the risk.
You can use Vulert, which analyzes your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
