Malicious Code Injection in cooperative_hamster_0xrequest Package
Summary
MAL-2025-101000: Malicious code in cooperative_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The cooperative_hamster_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for applications relying on them.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the cooperative_hamster_0xrequest package, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to compromised applications, as developers may unknowingly use these malicious packages, exposing their projects to security threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cooperative_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 cooperative_hamster_0xrequest package and replace it with a trusted alternative. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The cooperative_hamster_0xrequest package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for cooperative_hamster_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
Using this package can expose your application to security risks, as it modifies critical files and repopulates the npm registry with malicious variants.
You should remove the cooperative_hamster_0xrequest package from your project and replace it with a secure alternative.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
