Malicious Code Injection in unique_wolf_z3n Package: A Threat to npm Users

unique_wolf_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97145: Malicious code in unique_wolf_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The unique_wolf_z3n package is part of the npm ecosystem, often used for various JavaScript applications. It has gained notoriety due to its involvement in the tea.xyz token reward campaign, which has led to the proliferation of malicious packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous derivative packages, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in the unique_wolf_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous similar malicious packages. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access and manipulation of package dependencies.

How To Fix

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

npm uninstall unique_wolf_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, consider removing the unique_wolf_z3n package from your project if it is not essential. You can do this by executing the following command: npm uninstall unique_wolf_z3n. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The unique_wolf_z3n package poses a significant security risk due to its malicious code that alters package configurations and publishes unauthorized variants. It is essential for developers to take immediate action by updating or removing this package and to implement monitoring tools like Vulert to safeguard their applications against future vulnerabilities.

See every vulnerability recorded for unique_wolf_z3n →

Share this vulnerability

FAQ

The unique_wolf_z3n package is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.

This vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising security and functionality.

If you have installed the unique_wolf_z3n package, it is recommended to uninstall it immediately and check for any unauthorized changes in your project.

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

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert for real-time monitoring.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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