Malware in kdrive-utils
The npm package kdrive-utils contains malware that provides full system compromise to attackers. Any system with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with kdrive-utils installed or running
- Ecosystems
- Attack vectors
- Affected entities
- kdrive-utils
The npm package kdrive-utils has been identified as containing malware. According to the GitHub Advisory (GHSA-v9x6-7mvw-mf22), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems where kdrive-utils was installed.
Indicators of compromise
- Packages
- kdrive-utils
Remediation
- Immediately remove the kdrive-utils package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Assume full system compromise and conduct forensic analysis
- Monitor affected systems for signs of persistent malware or backdoors
- Review system logs for unauthorized access or modifications
- Consider full system rebuild if critical infrastructure or sensitive data is involved
Sources
- GitHub Advisory GHSA-v9x6-7mvw-mf22 · GitHub Advisory Database
Cite this entry
"Malware in kdrive-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 26, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-kdrive-utils-4mktca
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package