Malicious Code Injection in illegal_wildfowl_z3n Package

illegal_wildfowl_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94926: Malicious code in illegal_wildfowl_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The illegal_wildfowl_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to its malicious intent, which poses risks to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the illegal_wildfowl_z3n package originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall illegal_wildfowl_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 illegal_wildfowl_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities in your project.

Conclusion

The illegal_wildfowl_z3n package poses a significant threat due to its malicious code that modifies package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for illegal_wildfowl_z3n →

Share this vulnerability

FAQ

The illegal_wildfowl_z3n package is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further security risks.

You should uninstall the illegal_wildfowl_z3n package immediately and check your package-lock.json file for any remnants of it.

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

Yes, 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 illegal_wildfowl_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