Malicious Code Injection in compatible_hyena_replicate_automation Package
Summary
MAL-2025-100751: Malicious code in compatible_hyena_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 compatible_hyena_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 manipulate package metadata and inflate developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains 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 compromising the integrity of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall compatible_hyena_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 workaround, you can avoid using the compatible_hyena_replicate_automation package altogether. If it is already in use, consider replacing it with a trusted alternative that provides similar functionality without the associated risks.
Conclusion
The compatible_hyena_replicate_automation package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor for any potential updates or alternatives to ensure the security of your projects.
See every vulnerability recorded for compatible_hyena_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should remove the package from your project and monitor for any updates or patches that may be released.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
