Malicious Code Injection in distant_turkey_replicate_automation Package
Summary
MAL-2025-101641: Malicious code in distant_turkey_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 distant_turkey_replicate_automation package is part of the npm ecosystem, typically used for automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the distant_turkey_replicate_automation package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which can compromise the integrity of the npm registry and potentially expose users to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distant_turkey_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 distant_turkey_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The distant_turkey_replicate_automation package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is essential to uninstall this package and monitor your projects for vulnerabilities using tools like Vulert to maintain security.
See every vulnerability recorded for distant_turkey_replicate_automation →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks due to the presence of malicious code.
You should uninstall the distant_turkey_replicate_automation package immediately using the command: npm uninstall distant_turkey_replicate_automation.
Currently, there are no patched versions available for the distant_turkey_replicate_automation package.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.
