Malicious Code Injection in Roasted Dingo Replicate Automation Package
Summary
MAL-2025-108166: Malicious code in roasted_dingo_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 'roasted_dingo_replicate_automation' package is part of the npm ecosystem and is associated with automation tasks. It is designed to facilitate various operations within the JavaScript environment. However, this package has been identified as part of a malicious campaign that exploits npm's package publishing system, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'roasted_dingo_replicate_automation' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, effectively flooding the npm registry with derivative packages. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to reputation damage and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall roasted_dingo_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, consider removing the 'roasted_dingo_replicate_automation' package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall roasted_dingo_replicate_automation'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'roasted_dingo_replicate_automation' package has been identified as a vector for malicious code injection, posing significant risks to developers and the npm ecosystem. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for roasted_dingo_replicate_automation →
FAQ
It is an npm package designed for automation tasks but has been compromised with malicious code.
The vulnerability can lead to unauthorized changes in your package.json file and may expose your project to further security risks.
You should uninstall the package immediately and monitor your project for any unusual activity.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
