Malicious Code Injection in regular_firefly_z3n: A Threat to npm Packages
Summary
MAL-2025-96247: Malicious code in regular_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 'regular_firefly_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through the automatic generation and publication of derivative packages. Its functionality has been compromised, making it susceptible to malicious exploitation.
Vulnerability Detail
The vulnerability in 'regular_firefly_z3n' originates from its association with a malicious campaign that employs autopublish scripts to manipulate package metadata. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall regular_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 this package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package-lock.json monitoring to prevent the installation of compromised packages.
Conclusion
The 'regular_firefly_z3n' package poses a significant security risk due to its malicious code injection capabilities. It is crucial to remove this package from your projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for regular_firefly_z3n →
FAQ
The primary risk is the potential for malicious code execution that can compromise your project's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should immediately uninstall the package using 'npm uninstall regular_firefly_z3n' and monitor your project for any unusual activity.
Yes, consider looking for other npm packages that provide similar functionality but have a good reputation and are not associated with malicious activities.
Vulert uses your package-lock.json file to monitor for vulnerabilities in your dependencies and provides real-time alerts, helping you maintain a secure application.
