Malicious Code Injection in alive_firefly_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93190: Malicious code in alive_firefly_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 alive_firefly_z3n is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's publishing system, generating numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores in exchange for token rewards, but this comes at the cost of integrity and security within the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the alive_firefly_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and creating random package names, often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly install these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has been known to flood npm with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alive_firefly_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 avoid using the alive_firefly_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using the following command to uninstall the package: npm uninstall alive_firefly_z3n.
Conclusion
The alive_firefly_z3n package poses a significant risk to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised packages. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for alive_firefly_z3n →
FAQ
The main threat is the injection of malicious code that modifies package.json files and floods the npm registry with compromised packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should immediately uninstall the package using the command npm uninstall alive_firefly_z3n and check for any other affected packages.
Currently, there is no patched version available for the alive_firefly_z3n package. It is recommended to remove the package entirely.
Vulert uses your package-lock.json to monitor and alert you in real-time about any open-source vulnerabilities, ensuring your software remains secure.
