Malicious Code Injection in overwhelming_goose_z3n Package: A Threat to npm Ecosystem

overwhelming_goose_z3n Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-122434: Malicious code in overwhelming_goose_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The overwhelming_goose_z3n package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses significant risks to users who may inadvertently install these compromised packages.

Vulnerability Detail

The vulnerability in the overwhelming_goose_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in a proliferation of derivative packages that can clutter the npm registry and potentially lead to security risks for developers and users alike. The origin of this issue is linked to the tea.xyz token reward campaign, which exploited npm's publishing mechanisms to distribute harmful code.

How To Fix

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

npm uninstall overwhelming_goose_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 workaround, you can avoid using the overwhelming_goose_z3n package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The overwhelming_goose_z3n package represents a significant threat within the npm ecosystem due to its malicious behavior. By understanding the nature of this vulnerability and taking proactive steps to remove affected packages, developers can safeguard their applications from potential risks. Utilizing tools like Vulert can further enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for overwhelming_goose_z3n →

Share this vulnerability

FAQ

It is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit the Vulert playground at Vulert Scanner to check if your application is affected.

Using this package can lead to security vulnerabilities, cluttering of the npm registry, and potential exposure to malicious code that could affect your application.

There is no patch available for this specific package. The best course of action is to uninstall it and monitor your dependencies for any malicious activity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall overwhelming_goose_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