Malicious Code Vulnerability in exceptional_elk_z3n Package

exceptional_elk_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102315: Malicious code in exceptional_elk_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The exceptional_elk_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and users who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the exceptional_elk_z3n package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The ramifications include potential security risks, such as unauthorized access to sensitive data, and the degradation of the npm ecosystem due to the proliferation of these malicious packages.

How To Fix

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

npm uninstall exceptional_elk_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 exceptional_elk_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The exceptional_elk_z3n package poses a significant security risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for exceptional_elk_z3n →

Share this vulnerability

FAQ

The exceptional_elk_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially exposing your project to security risks and degrading the npm ecosystem.

You should uninstall the exceptional_elk_z3n package immediately using 'npm uninstall exceptional_elk_z3n' and check for any alternative packages.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

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

How To Fix

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

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