Malicious Code Injection in exciting_ape_z3n: A Threat to npm Ecosystem

exciting_ape_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102338: Malicious code in exciting_ape_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 package 'exciting_ape_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers who may unknowingly incorporate these packages into their projects.

Vulnerability Detail

The vulnerability in 'exciting_ape_z3n' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags and alter version numbers. This allows the package to continuously republish variants with Indonesian-themed names, polluting the npm registry. The ramifications include potential exposure of sensitive information, as private flags are removed, and the risk of integrating malicious code into legitimate projects.

How To Fix

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

npm uninstall exciting_ape_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 'exciting_ape_z3n' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The 'exciting_ape_z3n' package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is essential 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 exciting_ape_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the exposure of sensitive information and the risk of integrating malicious code, which can compromise the security of your application.

Immediately uninstall the package using 'npm uninstall exciting_ape_z3n' and check your package-lock.json for any lingering references.

Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

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