Malicious Code Vulnerability in boring_hamster_0xrequest Package
Summary
MAL-2025-100052: Malicious code in boring_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 boring_hamster_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm environment but has been compromised to include malicious scripts that can harm the integrity of the npm registry. The package is known for generating and publishing derivative packages with random names, which can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the boring_hamster_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using the package, and a compromised reputation for the npm ecosystem. The malicious payload is designed to exploit the npm publishing process, making it a significant threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall boring_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 workaround, you can avoid using the boring_hamster_0xrequest package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit similar vulnerabilities.
Conclusion
The boring_hamster_0xrequest package contains a significant vulnerability due to the presence of malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for boring_hamster_0xrequest →
FAQ
The boring_hamster_0xrequest package is an npm package that has been compromised to include malicious scripts aimed at manipulating the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should remove the boring_hamster_0xrequest package from your project and monitor for any updates or patches that may be released.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert uses package-lock.json to alert you of any issues without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
