Malicious Code Injection in interior_gopher_z3n Package - npm Vulnerability
Summary
MAL-2025-104337: Malicious code in interior_gopher_z3n (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 interior_gopher_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the interior_gopher_z3n package, which is linked to the tea.xyz token reward campaign. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also undermines the trustworthiness of the ecosystem, potentially allowing for further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall interior_gopher_z3nIf 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 interior_gopher_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The interior_gopher_z3n package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and stay vigilant by using tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for interior_gopher_z3n →
FAQ
The interior_gopher_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application by introducing malicious code.
You should uninstall the interior_gopher_z3n package immediately and monitor your application for any unusual behavior.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
