Malicious Code Injection in Dying Leopard Z3N Package - npm Vulnerability

dying_leopard_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94144: Malicious code in dying_leopard_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 'dying_leopard_z3n' package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate automated publishing of derivative packages, which can mislead developers and inflate reputation scores for token rewards. This package is particularly vulnerable due to its inclusion of scripts that modify package metadata and republish variants, leading to potential abuse of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious scripts that modify the 'package.json' file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The continuous republishing of these variants can lead to pollution of the registry, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall dying_leopard_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 measure, avoid using the 'dying_leopard_z3n' package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The 'dying_leopard_z3n' package poses a significant threat to developers using npm due to its malicious behavior. It is essential to remove this package and monitor your dependencies to maintain the security of your projects. Utilizing tools like Vulert can further enhance your ability to detect and respond to vulnerabilities.

See every vulnerability recorded for dying_leopard_z3n →

Share this vulnerability

FAQ

It is a malicious npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its integrity and security.

You should uninstall the package immediately using 'npm uninstall dying_leopard_z3n' and check your project for any other affected dependencies.

Regularly update your dependencies, monitor your project with tools like Vulert, and be cautious when adding new packages from npm.

Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can check if your application is affected by visiting Vulert Scanner.

How To Fix

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

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