Malicious Code Injection in immense_wildcat_z3n Package

immense_wildcat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94937: Malicious code in immense_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The immense_wildcat_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the immense_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 leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload is designed to execute autopublish scripts that automate the creation of these harmful derivatives, posing a significant risk to developers and users relying on the npm ecosystem.

How To Fix

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

npm uninstall immense_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 workaround, you can temporarily avoid using the immense_wildcat_z3n package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The immense_wildcat_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful derivatives. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the security of your applications.

See every vulnerability recorded for immense_wildcat_z3n →

Share this vulnerability

FAQ

The immense_wildcat_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code and potentially affecting other packages in your project.

If you have installed the immense_wildcat_z3n package, you should uninstall it immediately using the command: npm uninstall immense_wildcat_z3n.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities without signing up at the Vulert playground.

Yes, you should look for well-reviewed and actively maintained packages that serve the same purpose as immense_wildcat_z3n, ensuring they have a good reputation in the community.

How To Fix

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

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