Malicious Code Injection in interested_pigeon_z3n Package
Summary
MAL-2025-95083: Malicious code in interested_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 interested_pigeon_z3n package is part of the npm ecosystem and was associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the interested_pigeon_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This behavior pollutes the npm registry and can potentially harm developers' reputations and the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall interested_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 measure, you can prevent the installation of the affected package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include interested_pigeon_z3n in its dependencies.
Conclusion
The interested_pigeon_z3n package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is essential to remove this package from your project and monitor your dependencies for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for interested_pigeon_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall interested_pigeon_z3n' and check for any other affected packages.
Currently, there is no specific patched version for interested_pigeon_z3n. It is recommended to remove the package entirely.
Vulert uses the package-lock.json file to monitor your dependencies and alert you in real-time about any open-source vulnerabilities.
