Malicious Code Injection in average_wildcat_z3n Package

average_wildcat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99687: Malicious code in average_wildcat_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 average_wildcat_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be linked to a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to provide developers with tools and libraries, but it has been compromised to serve malicious purposes, including the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the average_wildcat_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores and pollute the npm registry with unwanted packages. The malicious code can lead to significant ramifications, including the potential for developers to inadvertently use compromised packages, which can introduce security risks into their applications.

How To Fix

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

npm uninstall average_wildcat_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 average_wildcat_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The average_wildcat_z3n package has been identified as malicious, posing significant risks to developers and their projects. It is crucial to uninstall this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for average_wildcat_z3n →

Share this vulnerability

FAQ

The average_wildcat_z3n package is an npm package that has been identified as malicious, linked to a token reward campaign that generates and publishes derivative packages.

The vulnerability can lead to the introduction of unwanted and potentially harmful packages into your project, which can compromise its security and integrity.

If you have installed the average_wildcat_z3n package, you should uninstall it immediately using 'npm uninstall average_wildcat_z3n' and review your project for any other compromised packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality but are known to be secure and free from malicious code.

How To Fix

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

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