Malicious Code Injection in absent_hawk_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-99040: Malicious code in absent_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 absent_hawk_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous variants to inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the absent_hawk_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall absent_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, you can prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Ensure that you do not include absent_hawk_z3n in your package.json or package-lock.json files.
Conclusion
The absent_hawk_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying proactive in managing dependencies will help safeguard your applications.
See every vulnerability recorded for absent_hawk_z3n →
FAQ
The impact includes potential exposure to malicious code that can compromise your project and pollute the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software by analyzing your package-lock.json file. Visit Vulert Scanner to check for vulnerabilities without any signup.
You should uninstall the package immediately using 'npm uninstall absent_hawk_z3n' and review your project for any other affected dependencies.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security updates in the npm ecosystem.
