Malicious Code Injection in flying_hawk_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-102839: Malicious code in flying_hawk_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
The 'flying_hawk_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 numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, making them a significant concern for the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'flying_hawk_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute 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 tainted packages, leading to potential security breaches and loss of trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall flying_hawk_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, avoid using the 'flying_hawk_z3n' package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'flying_hawk_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects from potential security breaches.
See every vulnerability recorded for flying_hawk_z3n →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
Using this package can lead to unauthorized modifications in your project, potentially compromising its security and integrity.
Immediately uninstall the package using 'npm uninstall flying_hawk_z3n' and check your package-lock.json for any references to it.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
