Malicious Code Injection in electronic_lemur_replicate_automation Package
Summary
MAL-2025-102028: Malicious code in electronic_lemur_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 electronic_lemur_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 floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through the generation and publication of numerous variants with altered names and metadata.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that exploits npm's publishing system. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to the pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall electronic_lemur_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 measure, you can avoid using the electronic_lemur_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 package dependencies for vulnerabilities.
Conclusion
The electronic_lemur_replicate_automation package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for electronic_lemur_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been compromised to serve malicious purposes.
Using this package can lead to the exposure of your application to security risks, including the potential for malicious code execution.
You should uninstall the package immediately and check for any dependencies that may be affected.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring an account.
