Malicious Code Injection in comparable_elk_z3n: A Threat to npm Users

comparable_elk_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93660: Malicious code in comparable_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 package 'comparable_elk_z3n' is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised, making it a significant risk for users who may unknowingly install it.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the 'comparable_elk_z3n' package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. Users who install this package may inadvertently contribute to the spread of malicious code and face security risks in their applications.

How To Fix

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

npm uninstall comparable_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 measure, avoid using the 'comparable_elk_z3n' package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The 'comparable_elk_z3n' package poses a significant threat to npm users due to its malicious intent and ability to pollute the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help safeguard your applications from similar threats.

See every vulnerability recorded for comparable_elk_z3n →

Share this vulnerability

FAQ

It is a malicious npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

Installing this package can lead to the introduction of malicious code, compromising the security and integrity of your application.

You should uninstall the package immediately using 'npm uninstall comparable_elk_z3n' and check your project for any other affected dependencies.

Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.

How To Fix

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

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