Malware in debugcli
The npm package debugcli was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-86fh-6m37-f9v4 was published on 2026-07-07.
- Disclosed
- Last updated
- Blast radius
- Any system with debugcli installed or running
- Ecosystems
- Attack vectors
- Affected entities
- debugcli
The npm package debugcli was identified as containing malware. According to the GitHub Security Advisory, any computer that has this package installed or running should be considered fully compromised, indicating the malware grants complete control to an outside entity.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems where debugcli was installed.
Indicators of compromise
- Packages
- debugcli
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the debugcli package from all affected systems
- Conduct a full security audit of any system that had debugcli installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review system logs and network traffic for indicators of compromise
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-86fh-6m37-f9v4 · GitHub Advisory Database
Cite this entry
"Malware in debugcli." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-debugcli-i9ssjh
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