Malicious Code Injection in free_pheasant_z3n Package

free_pheasant_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94604: Malicious code in free_pheasant_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 free_pheasant_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods npm with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, posing significant risks to users and developers alike.

Vulnerability Detail

The vulnerability in the free_pheasant_z3n package stems from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The malicious payload can compromise the integrity of the npm registry and potentially affect users who unknowingly install these packages, resulting in security risks and reputational damage.

How To Fix

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

npm uninstall free_pheasant_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 remove the free_pheasant_z3n package from your project by executing the following command: npm uninstall free_pheasant_z3n. This will prevent any potential malicious code from executing in your application.

Conclusion

The free_pheasant_z3n package has been identified as a vector for malicious code injection, posing significant risks to users and developers. It is essential to take immediate action by updating or uninstalling the package and utilizing monitoring tools like Vulert to safeguard your projects.

See every vulnerability recorded for free_pheasant_z3n →

Share this vulnerability

FAQ

The free_pheasant_z3n package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The malicious code modifies your package.json file, potentially compromising your project's integrity and leading to the installation of unwanted or harmful packages.

If you have installed the free_pheasant_z3n package, it is crucial to uninstall it immediately and check for any other affected packages in your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.

To prevent future vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for any potential threats.

How To Fix

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

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