Malicious Code Injection in testy_gopher_0xrequest Package
Summary
MAL-2025-109567: Malicious code in testy_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 testy_gopher_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, 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 scripts that publish numerous variants with altered names and metadata.
Vulnerability Detail
The vulnerability in the testy_gopher_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself and its variants, polluting the npm registry. The malicious payload can lead to unauthorized access and manipulation of the npm ecosystem, potentially affecting developers and users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall testy_gopher_0xrequest
If 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 prevent the installation of the testy_gopher_0xrequest package by using npm's package-lock.json to lock your dependencies. Ensure that your project does not include this package by removing it from your package.json and running npm install to refresh your dependencies.
Conclusion
The testy_gopher_0xrequest package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for testy_gopher_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.
The vulnerability can lead to unauthorized modifications in your project dependencies, potentially compromising the integrity and security of your application.
You should immediately remove the testy_gopher_0xrequest package from your project and check for any unauthorized changes in your codebase.
You can use tools like Vulert, which monitors your package-lock.json 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 needing to sign up.