Malicious Code Injection in few_falcon_z3n Package - npm Vulnerability

few_falcon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94492: Malicious code in few_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The few_falcon_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the few_falcon_z3n package stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of dependent projects. The malicious payload is specifically designed to inflate developer reputation scores for token rewards, posing a significant risk to the npm ecosystem.

How To Fix

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

npm uninstall few_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 temporary workaround, you can avoid using the few_falcon_z3n package and replace it with a trusted alternative. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.

Conclusion

The few_falcon_z3n package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for few_falcon_z3n →

Share this vulnerability

FAQ

The few_falcon_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

You should remove the few_falcon_z3n package from your project immediately and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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