Malicious Code Injection in upset_elk_z3n Package: A Threat to npm Ecosystem

upset_elk_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110215: Malicious code in upset_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 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 upset_elk_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, leading to significant security concerns for developers and users alike.

Vulnerability Detail

The vulnerability in the upset_elk_z3n package stems from its association with the tea.xyz token reward campaign, which aims to manipulate npm's reputation system. The malicious code embedded within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages.

How To Fix

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

npm uninstall upset_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 upset_elk_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always ensure to review the package's reputation and user feedback before integrating it into your project.

Conclusion

The upset_elk_z3n package poses a significant security threat due to its malicious code designed to manipulate the npm ecosystem. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for upset_elk_z3n →

Share this vulnerability

FAQ

The upset_elk_z3n package is a JavaScript package available on npm, designed to assist developers in building applications. However, it has been identified as part of a malicious campaign.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed the upset_elk_z3n package, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always verify the package's credibility before use.

How To Fix

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

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