Malicious Code Injection in wonderful_gopher_z3n: A Threat to npm Packages

wonderful_gopher_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92320: Malicious code in wonderful_gopher_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

wonderful_gopher_z3n is an npm package that has been implicated in a malicious campaign targeting the npm registry. This package is part of a broader initiative that aims to exploit the npm ecosystem by generating and publishing numerous derivative packages with the intent of inflating developer reputation scores for token rewards. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers who may unknowingly use it.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to automatically modify package.json files by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to confusion and potential security risks for developers relying on legitimate packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall wonderful_gopher_z3n

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 measure, avoid using the wonderful_gopher_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The wonderful_gopher_z3n package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects to maintain security and integrity. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for wonderful_gopher_z3n →

Share this vulnerability

FAQ

wonderful_gopher_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially causing conflicts and security risks in your project.

You should uninstall the package immediately using the command: npm uninstall wonderful_gopher_z3n.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall wonderful_gopher_z3n

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback