Malicious Code Injection in passing_pigeon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95850: Malicious code in passing_pigeon_z3n (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 'passing_pigeon_z3n' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The package's functionality is compromised by malicious code that alters its behavior and impacts the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'passing_pigeon_z3n' originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation involves modifying the package.json file to remove private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation by malicious actors. The ramifications include loss of trust in the npm ecosystem and increased risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall passing_pigeon_z3nIf 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 'passing_pigeon_z3n' package altogether. If it is already in use, consider removing it from your package.json and reinstalling your dependencies without it. Use the following command to remove the package: npm uninstall passing_pigeon_z3n.
Conclusion
The 'passing_pigeon_z3n' package poses a significant threat due to its malicious code that alters package metadata and can lead to npm registry pollution. It is crucial to remove this package from your project and stay informed about potential patches. Utilizing tools like Vulert can help you monitor for vulnerabilities in your dependencies effectively.
See every vulnerability recorded for passing_pigeon_z3n →
FAQ
'passing_pigeon_z3n' is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks and dependency confusion attacks.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
