Malware in @qlik/sprout-icons
Malware was discovered in the npm package @qlik/sprout-icons. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @qlik/sprout-icons
A malware incident was identified in the npm package @qlik/sprout-icons, published on GitHub's advisory database on 2026-08-04. Any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting all users of the affected package version(s).
Indicators of compromise
- Packages
- @qlik/sprout-icons
Remediation
- Immediately isolate any computer with @qlik/sprout-icons installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @qlik/sprout-icons package from all affected systems
- Perform a full security audit and malware scan on all affected systems
- Review access logs and monitor for unauthorized activity on systems that had the package installed
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-4hhj-rpx3-pw9f · GitHub Advisory Database
Cite this entry
"Malware in @qlik/sprout-icons." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-qlik-sprout-icons-1g6p8k
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in @servicetitan/table
Malware was discovered in the npm package @servicetitan/table. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate, unaffected computer.
npmCompromised package - containedcritical
Malware in @servicetitan/standalone-root
Malware was discovered in the npm package @servicetitan/standalone-root, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/anvil2-mcp
Malware was discovered in the npm package @servicetitan/anvil2-mcp. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/docs-uikit
Malware was discovered in the npm package @servicetitan/docs-uikit. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
npmCompromised package