Malicious Code Exploit in unhappy_firefly_z3n Package - npm Vulnerability
Summary
MAL-2025-110112: Malicious code in unhappy_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 unhappy_firefly_z3n package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on npm. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. It modifies key files such as package.json to remove private flags and alters version numbers, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability in the unhappy_firefly_z3n package stems from its malicious payload that modifies the package.json file, removing private flags and changing version numbers. This behavior is part of a broader scheme to flood the npm registry with derivative packages that have randomized names, ultimately polluting the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes developers to publish numerous packages, often leading to the inclusion of harmful scripts.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unhappy_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 workaround, you can avoid using the unhappy_firefly_z3n package and monitor your project for any dependencies that might indirectly include it. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities.
Conclusion
The unhappy_firefly_z3n package poses a significant risk due to its malicious code that alters essential files and floods the npm registry with harmful packages. It is crucial to uninstall this package and monitor your project for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for unhappy_firefly_z3n →
FAQ
It is a package associated with the tea.xyz token reward campaign, known for generating and publishing numerous derivative packages on npm.
The vulnerability can lead to the pollution of your npm registry and may compromise the integrity of your project by introducing malicious scripts.
You should uninstall the unhappy_firefly_z3n package immediately and check your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
