Malicious Code Injection in divine_wildcat_replicate_automation Package
Summary
MAL-2025-101685: Malicious code in divine_wildcat_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 divine_wildcat_replicate_automation package is part of the npm ecosystem, typically used for automation tasks. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the divine_wildcat_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 these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall divine_wildcat_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 divine_wildcat_replicate_automation package from your project by executing: npm uninstall divine_wildcat_replicate_automation. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The divine_wildcat_replicate_automation package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their projects.
See every vulnerability recorded for divine_wildcat_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been compromised with malicious code.
The malicious code modifies your package.json, potentially leading to security vulnerabilities and pollution of the npm registry.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without signup.
You can uninstall the package as a temporary measure to mitigate the risk until a secure version is available.
Detailed information can be found in the vulnerability report and by checking the package repository for updates.
