Malicious Code Injection in Decisive Fowl Z3N Package
Summary
MAL-2025-93939: Malicious code in decisive_fowl_z3n (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
Decisive Fowl Z3N is an npm package that was part of the tea.xyz token reward campaign. This campaign involved the creation of numerous packages that were designed to inflate developer reputation scores through automated publishing scripts. The package is primarily used for token rewards but has been compromised to include malicious code.
Vulnerability Detail
The vulnerability originates from the package's malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, such as the exposure of sensitive data and the degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall decisive_fowl_z3nIf 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 prevent the installation of the malicious package by using the following command to uninstall it: npm uninstall decisive_fowl_z3n. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The decisive_fowl_z3n package contains malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and stay vigilant about the packages you use. Regular audits and monitoring can help mitigate such vulnerabilities.
See every vulnerability recorded for decisive_fowl_z3n →
FAQ
The malicious code can lead to the exposure of sensitive information and the pollution of the npm registry, affecting the integrity of the ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Yes, regularly audit your dependencies using npm audit and remove any suspicious packages immediately.
Uninstall the package using npm uninstall decisive_fowl_z3n and check for any other dependencies that may be affected.
Yes, you can report vulnerabilities to the package maintainers or through platforms like GitHub to help improve the security of the ecosystem.
