Malicious Code Injection in wicked_gamefowl_z3n Package

wicked_gamefowl_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110893: Malicious code in wicked_gamefowl_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 wicked_gamefowl_z3n package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, contains scripts that manipulate package metadata and republish variants to the npm registry, leading to potential security risks.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the wicked_gamefowl_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates 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 exploits npm packages to gain undeserved reputation scores. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised development environment.

How To Fix

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

npm uninstall wicked_gamefowl_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 temporarily avoid using the wicked_gamefowl_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes by regularly reviewing your package.json and package-lock.json files.

Conclusion

The wicked_gamefowl_z3n package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to remove this package from your project and monitor for any unauthorized changes to maintain a secure development environment.

See every vulnerability recorded for wicked_gamefowl_z3n →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry.

You should uninstall the wicked_gamefowl_z3n package immediately using 'npm uninstall wicked_gamefowl_z3n' and check your package-lock.json for any remnants.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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