Malicious Code Injection in hot_elephant_z3n Package: npm Vulnerability Overview

hot_elephant_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94871: Malicious code in hot_elephant_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 hot_elephant_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the hot_elephant_z3n package originates from its malicious payload, which 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 affecting developers who rely on these packages. The malicious scripts included in this package are designed to automate the publication process, making it difficult to track and mitigate the impact of the malicious activity.

How To Fix

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

npm uninstall hot_elephant_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 avoid using the hot_elephant_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The hot_elephant_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for hot_elephant_z3n →

Share this vulnerability

FAQ

The hot_elephant_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing security risks.

If you have installed the hot_elephant_z3n package, it is recommended to remove it from your project immediately and check for alternative packages.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

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 hot_elephant_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