Malicious Code Injection in serious_hare_z3n Package - npm Vulnerability
Summary
MAL-2025-96534: Malicious code in serious_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 serious_hare_z3n package is part of the npm ecosystem and has been identified as a component of a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that alter its functionality and impact the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the serious_hare_z3n package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing them to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall serious_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 remove the serious_hare_z3n package from your project by running: npm uninstall serious_hare_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The serious_hare_z3n package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in maintaining the security of your projects.
See every vulnerability recorded for serious_hare_z3n →
FAQ
The serious_hare_z3n package is an npm package that was part of a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially exposing your project to further security risks.
You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
