Malicious Code Injection in dirty_lizard_replicate_automation Package
Summary
MAL-2025-101596: Malicious code in dirty_lizard_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 dirty_lizard_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 automatic generation and publication of numerous variants, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the dirty_lizard_replicate_automation package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential exploitation and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dirty_lizard_replicate_automation
If 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 remove the dirty_lizard_replicate_automation package from your project by executing: npm uninstall dirty_lizard_replicate_automation. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The dirty_lizard_replicate_automation package poses a significant security risk due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial for developers to be aware of such vulnerabilities and take immediate action to secure their projects by updating or removing affected packages.
See every vulnerability recorded for dirty_lizard_replicate_automation →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately and monitor your project for any unusual behavior.
Yes, you can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software without requiring access to the code.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.