Malicious Code Injection in mere_pigeon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-88421: Malicious code in mere_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 'mere_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 packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to automate the publishing process, which can lead to significant issues within the npm registry.
Vulnerability Detail
The vulnerability in 'mere_pigeon_z3n' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mere_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 prevent the installation of 'mere_pigeon_z3n' by using npm's package-lock.json file to lock your dependencies to known safe versions. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'mere_pigeon_z3n' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with harmful variants. It is essential for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their projects.
See every vulnerability recorded for mere_pigeon_z3n →
FAQ
'mere_pigeon_z3n' is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting your project's dependencies.
You should remove 'mere_pigeon_z3n' from your project and monitor for any updates or patches that may address the vulnerability.
Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and keep your packages updated to minimize risks.
You can find detailed information about this vulnerability in the Open Source Vulnerability database or by visiting the Vulert website.
