Malicious Code Injection in single_firefly_z3n Package
Summary
MAL-2025-96601: Malicious code in single_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The single_firefly_z3n package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of numerous packages aimed at inflating developer reputation scores. This package, like others in the campaign, is designed to automatically publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the single_firefly_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the unintentional exposure of sensitive information and the proliferation of untrustworthy packages in the npm registry. This behavior is indicative of a broader trend where malicious actors exploit npm for personal gain, potentially compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall single_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 prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include single_firefly_z3n in its dependencies. You can also utilize tools like Vulert to monitor for vulnerabilities in your package-lock.json file.
Conclusion
The single_firefly_z3n package poses a significant risk due to its malicious code that alters package metadata and proliferates untrustworthy packages. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for single_firefly_z3n →
FAQ
The single_firefly_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.
The vulnerability can lead to the exposure of sensitive information and the proliferation of untrustworthy packages, potentially compromising your project's integrity.
You should uninstall the single_firefly_z3n package immediately and check for any dependencies that may rely on it.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
