Malicious Code Injection in dead_firefly_requirement Package
Summary
MAL-2025-93920: Malicious code in dead_firefly_requirement (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 dead_firefly_requirement package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically include scripts that automate the generation and publication of derivative packages, aiming to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the dead_firefly_requirement package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The source of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dead_firefly_requirementIf 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 dead_firefly_requirement package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall dead_firefly_requirement.
Conclusion
The dead_firefly_requirement package contains a significant vulnerability that can compromise your project's integrity by modifying essential files and republishing malicious variants. It is crucial to monitor your dependencies and take immediate action to mitigate risks associated with this package.
See every vulnerability recorded for dead_firefly_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.
The vulnerability can lead to the modification of your package.json file and the introduction of unwanted packages, compromising your project's integrity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
As a temporary measure, consider uninstalling the dead_firefly_requirement package until a secure version is available.
