Malicious Code Injection in then_fly_z3n Package - npm Vulnerability

then_fly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96981: Malicious code in then_fly_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The then_fly_z3n package is part of the npm ecosystem, often used in JavaScript projects. It has been identified as part of a larger campaign that aims to exploit the npm registry by flooding it with malicious packages. These packages typically contain scripts that manipulate package metadata and publish numerous variants to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the then_fly_z3n package originates from its association with the tea.xyz token reward campaign. It includes malicious code that 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, which pollutes the npm registry and can compromise the integrity of projects relying on this package.

How To Fix

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

npm uninstall then_fly_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 workaround, you can manually remove the then_fly_z3n package from your project by executing the following command in your terminal: npm uninstall then_fly_z3n. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The then_fly_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for then_fly_z3n →

Share this vulnerability

FAQ

The then_fly_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and floods the npm registry.

If you have installed the then_fly_z3n package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall then_fly_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