Malicious Code Injection in comfortable_flea_replicate_automation Package
Summary
MAL-2025-100707: Malicious code in comfortable_flea_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 comfortable_flea_replicate_automation package is part of the npm ecosystem, often utilized in JavaScript projects for automation tasks. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that generates and publishes numerous derivative packages with randomized names. These packages contain scripts that modify the package.json file, removing private flags and changing version numbers, which can lead to the pollution of the npm registry and inflate developer reputation scores fraudulently. This malicious behavior poses significant risks, including the potential for unauthorized access and manipulation of applications that utilize this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comfortable_flea_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 comfortable_flea_replicate_automation package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using Vulert to detect any vulnerabilities in real-time.
Conclusion
The comfortable_flea_replicate_automation package poses significant security risks due to its association with malicious activities. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the safety and integrity of your applications.
See every vulnerability recorded for comfortable_flea_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been identified as part of a malicious campaign.
The vulnerability can lead to unauthorized modifications in your application, potentially compromising its security and integrity.
You should uninstall the package immediately and replace it with a trusted alternative.
You can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
There is no patch for the comfortable_flea_replicate_automation package; the best course of action is to remove it from your project.
