Malicious Code Injection in other_gopher_0xrequest Package - npm Vulnerability
Summary
MAL-2025-106817: Malicious code in other_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 'other_gopher_0xrequest' package is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify the package.json file, remove private flags, and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It modifies the package.json to remove private flags and changes version numbers, which can lead to unauthorized access and misuse of the package. The continuous republishing of variants can also lead to a polluted npm registry, making it difficult for developers to find legitimate packages. This vulnerability poses significant risks to developers relying on npm for package management, as it can compromise the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall other_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 workaround, you can avoid using the 'other_gopher_0xrequest' package entirely and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'other_gopher_0xrequest' package poses a significant security risk due to its malicious nature, which can compromise the integrity of applications using it. It is crucial to remove this package and monitor for vulnerabilities to ensure the safety of your projects.
See every vulnerability recorded for other_gopher_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can compromise the integrity of your application by allowing unauthorized modifications to your package.json file and polluting the npm registry.
You should uninstall the 'other_gopher_0xrequest' package immediately and look for alternative packages to avoid potential security risks.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
