Malicious Code Injection in subjective_hawk_z3n Package
Summary
MAL-2025-90778: Malicious code in subjective_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 subjective_hawk_z3n package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to numerous malicious packages flooding the npm registry. This package, like others in its category, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the subjective_hawk_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this vulnerability is traced back to a campaign aimed at exploiting npm's package management system for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall subjective_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 remove the subjective_hawk_z3n package from your project by executing: npm uninstall subjective_hawk_z3n. This will prevent any malicious code from executing in your application.
Conclusion
The subjective_hawk_z3n package contains malicious code that poses significant risks to applications relying on it. It is essential to take immediate action by updating or removing the package to safeguard your project from potential exploitation. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for subjective_hawk_z3n →
FAQ
The malicious code can lead to the automatic generation of numerous derivative packages, which can clutter the npm registry and potentially introduce security risks to applications using these packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without requiring any installation.
If you cannot update the package due to compatibility issues, consider removing it from your project until a safe version is released.
The malicious payload modifies your package.json by removing private flags and changing version numbers, which can lead to unintended consequences in your application's dependency management.
To prevent similar vulnerabilities, regularly audit your dependencies, utilize tools like Vulert for real-time monitoring, and only install packages from trusted sources.
