Malicious Code Injection in still_hare_z3n Package - npm Vulnerability
Summary
MAL-2025-96778: Malicious code in still_hare_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 still_hare_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata. This behavior not only undermines the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly incorporate these compromised packages into their projects.
Vulnerability Detail
The vulnerability in the still_hare_z3n package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically modify their own metadata, including removing private flags and changing version numbers. The malicious payload continuously republishes variants of the package, which can lead to pollution of the npm registry and potentially compromise the security of applications that depend on these packages. Developers using this package may inadvertently expose their applications to security risks and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall still_hare_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 avoid using the still_hare_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The still_hare_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain the integrity and security of your software.
See every vulnerability recorded for still_hare_z3n →
FAQ
The still_hare_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application uses the still_hare_z3n package, it may be exposed to security risks and could inadvertently contribute to the pollution of the npm registry.
You should uninstall the still_hare_z3n package immediately and check your package-lock.json file for any references to it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
