Malicious Code Injection in imperial_gopher_requirement Package
Summary
MAL-2025-94939: Malicious code in imperial_gopher_requirement (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 imperial_gopher_requirement package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise the integrity of software projects relying on it. This package is particularly vulnerable due to its association with automated scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability stems from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall imperial_gopher_requirementIf 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, you can avoid using the imperial_gopher_requirement package and look for alternative packages that do not have known vulnerabilities. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The imperial_gopher_requirement package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for imperial_gopher_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign, which can compromise software projects.
Using this package can lead to the introduction of malicious code, which may compromise your project's security and integrity.
You should uninstall the package immediately and look for secure alternatives.
You can use Vulert, which monitors your package-lock.json for 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 without signing up.
