Malicious Code Injection in specific_wildfowl_requirement Package
Summary
MAL-2025-96706: Malicious code in specific_wildfowl_requirement (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The specific_wildfowl_requirement package is an npm module that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the npm ecosystem. However, this package has been identified as malicious, containing scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the specific_wildfowl_requirement package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm registry with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specific_wildfowl_requirementIf 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 measure, you can avoid using the specific_wildfowl_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly reviewed for any unauthorized changes.
Conclusion
The specific_wildfowl_requirement package poses a significant risk due to its malicious code designed to manipulate package management processes. It is essential to remove this package and monitor your project for any unauthorized changes to maintain security.
See every vulnerability recorded for specific_wildfowl_requirement →
FAQ
It is an npm package that has been identified as malicious, designed to generate and publish derivative packages for token rewards.
The malicious code can compromise your project's integrity by modifying package files and introducing unwanted packages into your environment.
You should uninstall the specific_wildfowl_requirement package immediately and check your project for any unauthorized changes.
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 without needing to sign up.
