Malicious Code Injection in bad_pigeon_replicate_automation: A Threat to npm Users
Summary
MAL-2025-99743: Malicious code in bad_pigeon_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 package 'bad_pigeon_replicate_automation' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the replication and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality includes generating random package names and modifying package.json files, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability in 'bad_pigeon_replicate_automation' stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. This code generates random package names and continuously republishes variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities. The ramifications include potential security risks for developers and users who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bad_pigeon_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 'bad_pigeon_replicate_automation' from your project by executing the command: 'npm uninstall bad_pigeon_replicate_automation'. This will prevent the execution of any malicious code associated with the package until a fix is applied.
Conclusion
The 'bad_pigeon_replicate_automation' package poses a significant threat due to its malicious code that alters package.json files and publishes unwanted packages. It is crucial for developers to update or remove this package to safeguard their projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for bad_pigeon_replicate_automation →
FAQ
It is an npm package involved in automating the publication of derivative packages, often linked to malicious activities.
The vulnerability can lead to the modification of your package.json file and the introduction of unwanted packages, compromising your project's integrity.
You should uninstall the package immediately and check for any unauthorized changes to your project files.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
