Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in qlkube

Malware was discovered in the npm package qlkube, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with qlkube installed or running
Ecosystems
Attack vectors
Affected entities
  • qlkube

A critical malware incident was identified in the npm package qlkube. According to the GitHub Advisory (GHSA-w88p-pj99-p5g3), any computer with this package installed or running should be considered fully compromised.

The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, unaffected computer. However, due to the nature of the compromise, there is no guarantee that removing the package alone will eliminate all malicious software that may have been installed as a result of the initial infection.

This represents a critical supply chain attack through a compromised package in the npm ecosystem.

Indicators of compromise

Packages
  • qlkube

Remediation

  • Remove the qlkube package immediately from all affected systems
  • Rotate all secrets, API keys, and credentials from a different, unaffected computer
  • Perform a full security audit and malware scan of any system that had qlkube installed
  • Review system logs and network activity for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) potentially compromised and plan for full rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-w88p-pj99-p5g3 · GitHub Advisory Database

Cite this entry

"Malware in qlkube." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-qlkube-16u0wd

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in myclaude-code

    Malware was discovered in the npm package myclaude-code. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

    npmCompromised package
  2. resolvedcritical

    Malware in clavue

    The npm package clavue contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  3. containedcritical

    Malware in airkey-mfa-react

    Malware was discovered in the npm package airkey-mfa-react. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.

    npmCompromised package
  4. resolvedcritical

    Malware in fusion-client

    The npm package fusion-client contained malware that provided full system compromise to attackers. Any computer with the package installed should be considered fully compromised and all secrets and keys rotated from a different machine.

    npmCompromised package