Malicious Code Injection in statutory_gopher_z3n Package
Summary
MAL-2025-109094: Malicious code in statutory_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The statutory_gopher_z3n package is part of the npm ecosystem, often utilized 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. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the statutory_gopher_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This behavior can lead to unauthorized access, data leakage, and a compromised development environment, as developers may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall statutory_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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected without needing to sign up.
Conclusion
The statutory_gopher_z3n package poses a significant security risk due to its malicious behavior. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for statutory_gopher_z3n →
FAQ
The statutory_gopher_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
This vulnerability can lead to unauthorized access and data leakage, as the package modifies critical files and repopulates the npm registry with malicious variants.
You should uninstall the statutory_gopher_z3n package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application using the Vulert playground.
There is no patch for the statutory_gopher_z3n package due to its malicious nature. The best course of action is to remove it from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
