Malicious Code Injection in thundering_firefly_z3n Package

thundering_firefly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97009: Malicious code in thundering_firefly_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The thundering_firefly_z3n package is part of the npm ecosystem, often used in JavaScript projects. It appears to be associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages.

Vulnerability Detail

The vulnerability in the thundering_firefly_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of projects that depend on this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall thundering_firefly_z3n

If 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 thundering_firefly_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The thundering_firefly_z3n package presents a significant vulnerability due to its involvement in a malicious campaign. It is crucial for developers to remove this package and monitor their dependencies for any potential threats. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for thundering_firefly_z3n →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove the thundering_firefly_z3n package from your project and monitor for any updates or patches.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software without requiring code access. You can use the Vulert playground to check if your application is affected.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall thundering_firefly_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback