Malicious Code Injection in poised_flea_z3n: A Threat to npm Users
Summary
MAL-2025-107118: Malicious code in poised_flea_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 poised_flea_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, posing significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in poised_flea_z3n originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of dependent applications. The malicious payload can result in unauthorized access to sensitive data and disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall poised_flea_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 remove the package from your project by executing the following command in your terminal: npm uninstall poised_flea_z3n. This will prevent the malicious code from executing in your application.
Conclusion
The poised_flea_z3n package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove this package from their projects to maintain the security and integrity of their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for poised_flea_z3n →
FAQ
poised_flea_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your application to security risks and instability.
You should uninstall the poised_flea_z3n package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
