Malicious Code Injection in Significant Falcon Z3N Package

significant_falcon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96581: Malicious code in significant_falcon_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Significant Falcon Z3N package is part of the npm ecosystem, often utilized in JavaScript projects. It has been identified as part of a broader campaign related to the tea.xyz token rewards, which has led to the proliferation of malicious packages. These packages are designed to manipulate the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the Significant Falcon Z3N package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which has been flooding npm with similar malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm ecosystem due to the proliferation of derivative packages.

How To Fix

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

npm uninstall significant_falcon_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 check your package-lock.json file for any instances of the Significant Falcon Z3N package and remove it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The Significant Falcon Z3N package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for significant_falcon_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

Using this package can lead to security risks and the pollution of your project's dependencies, potentially affecting its integrity.

You should remove the Significant Falcon Z3N package from your project and monitor your dependencies for any further vulnerabilities.

You can use tools like Vulert, which allows you to monitor your project in real-time for open-source vulnerabilities using just your package-lock.json.

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

How To Fix

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

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