Malicious Code Injection in static_hamster_0xrequest Package
Summary
MAL-2025-109083: Malicious code in static_hamster_0xrequest (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 static_hamster_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_hamster_0xrequestIf 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 static_hamster_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The static_hamster_0xrequest package poses a significant risk due to its malicious code designed to manipulate npm registry behaviors. Immediate action is required to remove this package and safeguard your application from potential threats.
See every vulnerability recorded for static_hamster_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The malicious code can compromise your application's integrity by modifying package configurations and introducing potentially harmful behaviors.
You should uninstall the static_hamster_0xrequest package immediately to prevent any potential exploitation.
Yes, consider using other reputable packages that offer similar functionalities without the risks associated with static_hamster_0xrequest.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.
