Malicious Code in qlkube-client (npm)

qlkube-client Updated 02 Oct 2025

Summary

05/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8432: Malicious code in qlkube-client (npm). Affects qlkube-client versions 1.0.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The qlkube-client package is an npm package that is used for interacting with Kubernetes clusters. It provides functionality for managing and controlling Kubernetes resources. The package is widely used in various applications and projects that leverage Kubernetes for container orchestration. However, the qlkube-client package has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The qlkube-client package has been flagged as malicious due to the following reasons:

  • The package communicates with a domain associated with malicious activity.
  • The package executes one or more commands associated with malicious behavior.

This indicates that the package may perform unauthorized actions or compromise the security of the system it is installed in. The presence of malicious code in the qlkube-client package poses a significant risk to the integrity and security of Kubernetes clusters and the applications that rely on them.

How To Fix

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

npm uninstall qlkube-client

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

There is no known workaround for this vulnerability. It is essential to take immediate action by removing the qlkube-client package and replacing it with a secure alternative.

Conclusion

The qlkube-client package has been identified as malicious, posing a significant risk to the security and integrity of Kubernetes clusters and the applications utilizing them. It is crucial to remove the package and replace it with a trusted alternative. Additionally, reviewing and securing the dependencies of the affected application or project is essential. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for qlkube-client →

Share this vulnerability

FAQ

qlkube-client is an npm package used for interacting with Kubernetes clusters.

The qlkube-client package has been flagged as malicious due to its communication with a domain associated with malicious activity and execution of commands associated with malicious behavior.

Using the qlkube-client package can lead to unauthorized actions, compromise the security of Kubernetes clusters, and put the applications relying on them at risk.

To fix the vulnerability, remove the qlkube-client package and replace it with a trusted and secure alternative. Also, review the dependencies of the application or project using the package and ensure they are from trusted sources without known vulnerabilities.

No, there is no known workaround for this vulnerability. Immediate action is required to remove the qlkube-client package and replace it with a secure alternative.

How To Fix

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

npm uninstall qlkube-client

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