Malicious Code Injection in Growing Dove Replicate Automation Package
Summary
MAL-2025-103408: Malicious code in growing_dove_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 'growing_dove_replicate_automation' package is part of the npm ecosystem, primarily utilized for automation tasks related to the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. However, it has been identified to contain malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers who may unknowingly use these compromised packages. The malicious payload can lead to unauthorized access and manipulation of project dependencies, posing significant risks to application security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall growing_dove_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 remove the 'growing_dove_replicate_automation' package from your project by executing the command: 'npm uninstall growing_dove_replicate_automation'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'growing_dove_replicate_automation' package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for growing_dove_replicate_automation →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes variants to the npm registry, potentially compromising other projects.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the vulnerability allows for unauthorized modifications to project dependencies, which can lead to broader security issues.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to your packages.
