Malicious Code Injection in super_hamster_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-109299: Malicious code in super_hamster_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 super_hamster_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks.
Vulnerability Detail
The vulnerability in the super_hamster_z3n package stems from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The ramifications include potential exposure to further malicious code and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall super_hamster_z3n
If 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 measure, avoid using the super_hamster_z3n package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The super_hamster_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and publishes unauthorized versions. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for super_hamster_z3n →
FAQ
super_hamster_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The malicious code can modify your package.json file, remove private flags, and publish unauthorized versions, potentially leading to security breaches.
You should uninstall the super_hamster_z3n package immediately and monitor your project for any unusual activity.
You can use Vulert's playground to analyze your package-lock.json file for vulnerabilities without needing to sign up.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities, making it easier to maintain secure applications.