Malicious Code Injection in arbitrary_wildfowl_z3n Package - npm Vulnerability

arbitrary_wildfowl_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93261: Malicious code in arbitrary_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 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 arbitrary_wildfowl_z3n package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of this package is to inflate developer reputation scores for rewards, but it poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the arbitrary_wildfowl_z3n package originates from its malicious intent to alter package.json files. It removes private flags, modifies version numbers, and generates random package names, leading to pollution of the npm registry. This behavior can compromise the security of applications relying on these packages, potentially introducing further vulnerabilities and instability.

How To Fix

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

npm uninstall arbitrary_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 workaround, consider using a package monitoring tool like Vulert, which can help you identify and alert you to open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The arbitrary_wildfowl_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. Immediate action is required to remove this package and safeguard your applications from potential vulnerabilities.

See every vulnerability recorded for arbitrary_wildfowl_z3n →

Share this vulnerability

FAQ

It is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the introduction of malicious code, compromising the security and stability of your application.

You should uninstall the arbitrary_wildfowl_z3n package immediately to mitigate any risks associated with its malicious behavior.

No, it is recommended to remove the package entirely as it is designed with malicious intent and does not have a safe version.

You can use tools like Vulert to monitor your project's dependencies for vulnerabilities in real-time.

How To Fix

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

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