Malicious Code Injection in breezy_goat_z3n Package

breezy_goat_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100093: Malicious code in breezy_goat_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 breezy_goat_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package was identified as part of a malicious campaign targeting developers by flooding the npm registry with derivative packages. Its primary function is to facilitate the tea.xyz token reward campaign, which incentivizes developers to publish packages. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the breezy_goat_z3n package, which includes scripts designed to modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. The ramifications include potential security breaches, loss of developer reputation, and the proliferation of untrustworthy packages within the ecosystem.

How To Fix

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

npm uninstall breezy_goat_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 prevent the installation of the breezy_goat_z3n package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The breezy_goat_z3n package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for breezy_goat_z3n →

Share this vulnerability

FAQ

breezy_goat_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your application to security risks and affecting its integrity.

You should immediately uninstall the breezy_goat_z3n package using npm uninstall breezy_goat_z3n and check your package-lock.json for any references to it.

Yes, you can use Vulert to monitor your application for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

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