Malware in @qlik/eslint-config
Malware was discovered in the npm package @qlik/eslint-config. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with @qlik/eslint-config installed
- Ecosystems
- Attack vectors
- Affected entities
- @qlik/eslint-config
A malicious version of the npm package @qlik/eslint-config was published, containing malware that compromises any system where it is installed or executed.\n\nAccording to the GitHub Advisory (GHSA-v3jf-cqwx-xcj6), any computer with this package installed should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer, and removing the package. However, due to the level of system compromise, removal of the package alone may not eliminate all malicious software installed as a result.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- @qlik/eslint-config
Remediation
- Immediately rotate all secrets, API keys, and credentials from a separate, uncompromised computer
- Remove the @qlik/eslint-config package from all affected systems
- Perform a full security audit and malware scan of all systems that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Notify any systems or services that may have been accessed using compromised credentials
Sources
- GitHub Advisory GHSA-v3jf-cqwx-xcj6 · GitHub Advisory Database
Cite this entry
"Malware in @qlik/eslint-config." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-qlik-eslint-config-kpxhns
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 @rentwise/common
Malware was discovered in the npm package @rentwise/common. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
npmCompromised package - containedcritical
Malware in @nasddatax/common
Malware was discovered in the npm package @nasddatax/common. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in @voxepay/checkout
The npm package @voxepay/checkout contained malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in @afasinatickets/common
The npm package @afasinatickets/common contains malware that grants full system compromise to an outside entity. All systems with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package