Malicious Code Injection in intermediate_pigeon_z3n: A Threat to npm Packages
Summary
MAL-2025-95100: Malicious code in intermediate_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 'intermediate_pigeon_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'intermediate_pigeon_z3n' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to alter package.json files. This manipulation removes private flags, changes version numbers, and generates random package names, which can lead to a compromised npm registry and potential security risks for developers relying on these packages. The continuous republishing of these variants can also degrade the quality of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intermediate_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 'intermediate_pigeon_z3n' package and monitor your project for any dependencies that may indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'intermediate_pigeon_z3n' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial for developers to be vigilant about the packages they use and to employ monitoring tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for intermediate_pigeon_z3n →
FAQ
The primary risk is the potential for malicious code to alter your package.json file, which can lead to security vulnerabilities and pollution of the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed 'intermediate_pigeon_z3n', you should remove it from your project and monitor for any updates or patches.
Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time.
Remove any malicious packages immediately and review your dependencies for any potential security risks.
