Malicious Code Injection in internal_gopher_0xrequest Package
Summary
MAL-2025-104353: Malicious code in internal_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 internal_gopher_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the internal_gopher_0xrequest package, which includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and applications relying on npm packages. The malicious payload can compromise the security of applications using this package, leading to unauthorized access or exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internal_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 workaround, you can avoid using the internal_gopher_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The internal_gopher_0xrequest package poses a significant security risk due to its malicious code that modifies package files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities.
See every vulnerability recorded for internal_gopher_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The malicious code can compromise your application's security by modifying package.json and republishing variants, potentially leading to unauthorized access.
You should uninstall the internal_gopher_0xrequest package immediately and check your dependencies for any lingering references.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code directly.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
