Malicious Code Injection in lost_pigeon_replicate_automation Package
Summary
MAL-2025-105328: Malicious code in lost_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 'lost_pigeon_replicate_automation' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate certain tasks, but it has been compromised to include malicious scripts that can manipulate its functionality and impact the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'lost_pigeon_replicate_automation' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic republishing of these variants. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry with potentially harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lost_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 the 'lost_pigeon_replicate_automation' package from your project by executing the command: 'npm uninstall lost_pigeon_replicate_automation'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'lost_pigeon_replicate_automation' package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats.
See every vulnerability recorded for lost_pigeon_replicate_automation →
FAQ
The malicious code modifies the package.json file, removes private flags, and generates random package names to inflate developer reputation scores.
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.
Using this package can lead to the pollution of the npm registry and may expose your application to further vulnerabilities or malicious activities.
Regularly monitor your dependencies and use tools like Vulert to stay informed about vulnerabilities in your open-source packages.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
