Malicious Code Injection in quick_flea_z3n Package
Summary
MAL-2025-96152: Malicious code in quick_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 quick_flea_z3n package is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is aimed at inflating developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability in the quick_flea_z3n package arises from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially harm developers by inflating their reputation scores through illegitimate means. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall quick_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 avoid using the quick_flea_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The quick_flea_z3n package poses a significant risk due to its malicious code that manipulates npm registry entries. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to safeguard their projects. Regular monitoring and using tools like Vulert can help in identifying and mitigating these risks effectively.
See every vulnerability recorded for quick_flea_z3n →
FAQ
The quick_flea_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The malicious code can alter your package's metadata, remove private flags, and lead to the republishing of variants, which can harm your project's integrity and reputation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed quick_flea_z3n, it is advisable to remove it from your project immediately and look for alternative packages.
Currently, there is no specific patch for the quick_flea_z3n package. The best course of action is to remove the package and monitor for any updates.
