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.
- 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
- 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.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting