Malicious Code Injection in select_elephant_z3n Package

select_elephant_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96495: Malicious code in select_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 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 select_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 token rewards for developers by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate its functionality and impact the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the select_elephant_z3n package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The origin of this issue is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting token reward schemes.

How To Fix

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

npm uninstall select_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 workaround, you can avoid using the select_elephant_z3n package and any other packages associated with the tea.xyz token reward campaign until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The select_elephant_z3n package has been identified as containing malicious code that compromises the integrity of the npm registry and poses a risk to developers. It is crucial to uninstall this package and monitor your project for any vulnerabilities to maintain security.

See every vulnerability recorded for select_elephant_z3n →

Share this vulnerability

FAQ

The select_elephant_z3n package is an npm package involved in the tea.xyz token reward campaign, which aims to reward developers with tokens for publishing packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, potentially leading to security vulnerabilities and reputation damage.

If you have installed the select_elephant_z3n package, you should uninstall it immediately using the command 'npm uninstall select_elephant_z3n' and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

Regularly audit your dependencies using tools like npm audit, keep your packages updated, and monitor for vulnerabilities using services like Vulert.

How To Fix

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

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