Malicious Code Injection in 'appropriate_wolverine_z3n' Package: A Threat to npm Ecosystem

appropriate_wolverine_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98620: Malicious code in appropriate_wolverine_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 'appropriate_wolverine_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to provide functionality for developers but has been compromised. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in 'appropriate_wolverine_z3n' originates from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to the execution of malicious code and compromise their applications.

How To Fix

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

npm uninstall appropriate_wolverine_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 'appropriate_wolverine_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall appropriate_wolverine_z3n.

Conclusion

The 'appropriate_wolverine_z3n' package poses a significant risk due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. Developers should take immediate action to remove this package and consider using tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for appropriate_wolverine_z3n →

Share this vulnerability

FAQ

It is an npm package that has been compromised and is part of a malicious campaign to inflate developer reputation scores.

Using this package can lead to the execution of malicious code, compromising your application's security and integrity.

You should immediately uninstall the package and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

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