Malicious Code Injection in Damaged Coral Replicate Automation Package
Summary
MAL-2025-101191: Malicious code in damaged_coral_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'damaged_coral_replicate_automation' package is part of a campaign that exploits the npm ecosystem, primarily targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified to contain malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'damaged_coral_replicate_automation' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall damaged_coral_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 'damaged_coral_replicate_automation' package altogether. Instead, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The 'damaged_coral_replicate_automation' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for damaged_coral_replicate_automation →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the introduction of malicious code into your project, compromising its integrity and security.
You should uninstall the package immediately and monitor your project for any signs of compromise.
Yes, tools like Vulert can help monitor your project's dependencies for vulnerabilities in real-time without requiring access to your code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
