Malware in @qlik/sprout-react
Malware was discovered in the npm package @qlik/sprout-react. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @qlik/sprout-react
A critical malware incident was identified in the npm package @qlik/sprout-react. According to the GitHub Security Advisory (GHSA-pc9r-8h2v-v6mw), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package may have granted outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile removing the package is recommended, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package compromise. A full security audit and potential system rebuild may be necessary for affected systems.
Indicators of compromise
- Packages
- @qlik/sprout-react
Remediation
- Immediately remove @qlik/sprout-react from all systems
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- Conduct a full security audit of any system that had the package installed
- Consider rebuilding affected systems from clean media
- Review system logs for any unauthorized access or activity during the period the package was installed
- Monitor for any signs of persistent malware or unauthorized access
Sources
- GitHub Advisory GHSA-pc9r-8h2v-v6mw · GitHub Advisory Database
Cite this entry
"Malware in @qlik/sprout-react." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-qlik-sprout-react-s9n8rt
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