Malicious Code Injection in colonial_gopher_0xrequest Package
Summary
MAL-2025-100667: Malicious code in colonial_gopher_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 colonial_gopher_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. This package was identified as part of a malicious campaign that aimed to exploit npm's publishing system. It is designed to automate the creation and publication of derivative packages, which can lead to reputation inflation for the tea protocol token rewards. The package's functionality is compromised, making it a potential threat to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in the colonial_gopher_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is part of a broader scheme to inflate developer reputation scores through the automatic generation of numerous derivative packages. This can result in security risks for users who unknowingly install these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall colonial_gopher_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 colonial_gopher_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.
Conclusion
The colonial_gopher_0xrequest package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security of their applications.
See every vulnerability recorded for colonial_gopher_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry by publishing numerous derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert's playground to check your application without any signup.
Using compromised packages can lead to security vulnerabilities, data breaches, and potential exploitation of your application by malicious actors.
It is recommended to audit your npm packages regularly, ideally after every significant update or addition of new packages, to ensure they are secure.
Remove the vulnerable package immediately and look for alternatives or updated versions that do not contain the vulnerability.
