Malware in @qlik/eslint-config-react
Malware was discovered in the npm package @qlik/eslint-config-react. 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/eslint-config-react
A malicious version of the npm package @qlik/eslint-config-react was identified and published to the npm registry. The package contained malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nThis incident was disclosed via GitHub Advisory GHSA-p827-gwm8-29x5 on 2026-08-04.
Indicators of compromise
- Packages
- @qlik/eslint-config-react
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, unaffected computer
- Remove the @qlik/eslint-config-react package from all affected systems
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging or replacement if the package was installed on production or sensitive systems
- Review npm package dependencies to identify any other potentially compromised packages
Sources
- GitHub Advisory GHSA-p827-gwm8-29x5 · GitHub Advisory Database
Cite this entry
"Malware in @qlik/eslint-config-react." 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-react-1rlh07
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package