Malicious Code Injection in average_gazelle_z3n Package

average_gazelle_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93317: Malicious code in average_gazelle_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The average_gazelle_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 that aims to exploit the npm registry by generating and publishing derivative packages with random names. Its primary functionality is compromised by the malicious code that alters package metadata, leading to potential security risks for developers and users relying on this package.

Vulnerability Detail

The vulnerability in the average_gazelle_z3n package originates from its association with a token reward campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to identify legitimate packages. The ramifications include potential security breaches and the risk of integrating compromised packages into applications.

How To Fix

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

npm uninstall average_gazelle_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 workaround, you can temporarily avoid using the average_gazelle_z3n package by removing it from your dependencies. If you need similar functionality, consider using alternative packages that are verified and have no known vulnerabilities.

Conclusion

The average_gazelle_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for average_gazelle_z3n →

Share this vulnerability

FAQ

The average_gazelle_z3n package 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 integration of malicious code into your application, potentially compromising its security and functionality.

If you have used the average_gazelle_z3n package, it is crucial to remove it from your project and check for any other dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies using tools like npm audit and consider using services like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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