Malicious Code Injection in associated_wildfowl_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99647: Malicious code in associated_wildfowl_0xrequest (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 associated_wildfowl_0xrequest package is part of the npm ecosystem, often utilized in JavaScript applications. It is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in the associated_wildfowl_0xrequest package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of derivative packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall associated_wildfowl_0xrequest

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, avoid using the associated_wildfowl_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The associated_wildfowl_0xrequest package contains a significant vulnerability that can lead to malicious code injection and pollution of the npm registry. It is crucial for developers to remove this package and monitor their projects for any similar threats. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for associated_wildfowl_0xrequest →

Share this vulnerability

FAQ

It is an npm package linked to the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the injection of malicious code, which may compromise your project's integrity and security.

You should uninstall the package immediately and check for any other potentially compromised packages in your project.

Yes, tools like Vulert can monitor 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 for vulnerabilities without requiring an account.

How To Fix

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

npm uninstall associated_wildfowl_0xrequest

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