Malicious Code Vulnerability in explicit_elephant_z3n Package

explicit_elephant_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102402: Malicious code in explicit_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 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 explicit_elephant_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publishing of derivative packages. This package, like others in the campaign, is intended to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the explicit_elephant_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it can lead to the pollution of the npm registry with numerous derivative packages, potentially compromising the integrity of the ecosystem and affecting developers' reputations.

How To Fix

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

npm uninstall explicit_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 temporary measure, you can prevent the installation of the explicit_elephant_z3n package by using the following command: npm uninstall explicit_elephant_z3n. Additionally, you can monitor your project for vulnerabilities using Vulert, which utilizes package-lock.json to alert you in real-time for open-source vulnerabilities.

Conclusion

The explicit_elephant_z3n package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for explicit_elephant_z3n →

Share this vulnerability

FAQ

The explicit_elephant_z3n package is part of a campaign that aims to inflate developer reputation scores in the npm ecosystem by automatically generating and publishing derivative packages.

The malicious code modifies your package.json file, potentially leading to the pollution of the npm registry and impacting your project's integrity and reputation.

You should update the package to a patched version if available or uninstall it entirely to mitigate the risk.

Yes, Vulert can monitor your project for vulnerabilities using package-lock.json and alert you in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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