Malicious Code Injection in internal_hamster_z3n Package - npm Vulnerability
Summary
MAL-2025-98766: Malicious code in internal_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 internal_hamster_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. The core functionality of this package has been compromised, making it a potential threat to developers and their applications.
Vulnerability Detail
The vulnerability in the internal_hamster_z3n package stems from its malicious code, which is designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The origin of this vulnerability is linked to a campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The ramifications include potential security risks for applications that depend on this package, as well as the degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internal_hamster_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 internal_hamster_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The internal_hamster_z3n package poses a significant threat due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies to ensure the security of their applications.
See every vulnerability recorded for internal_hamster_z3n →
FAQ
The internal_hamster_z3n package is an npm package that has been identified as malicious, part of a campaign to manipulate the npm registry.
If your application depends on the internal_hamster_z3n package, it may be at risk of security breaches and could contribute to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the internal_hamster_z3n package immediately and look for alternatives to mitigate any potential risks.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
