Malware in @qlik/eslint-config-base
Malware was discovered in the npm package @qlik/eslint-config-base. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @qlik/eslint-config-base
A critical malware incident was identified in the npm package @qlik/eslint-config-base. According to the GitHub Security Advisory (GHSA-mc8j-vx8m-ww53), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory recommends immediate rotation of all secrets and cryptographic keys from a separate, unaffected computer. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious artifacts, as the attacker may have gained full control of the affected system during the compromise.\n\nThis is a supply chain attack via a compromised npm package, affecting all users and systems that depend on @qlik/eslint-config-base.
Indicators of compromise
- Packages
- @qlik/eslint-config-base
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a clean, unaffected computer
- Remove @qlik/eslint-config-base from all affected systems
- Audit all systems that had this package installed for signs of unauthorized access or persistence mechanisms
- Review access logs and network traffic from affected systems for indicators of compromise
- Consider full system reimaging or replacement if the package was installed on production or sensitive systems
- Notify all users and downstream consumers of any software built with this package
Sources
- GitHub Advisory GHSA-mc8j-vx8m-ww53 · GitHub Advisory Database
Cite this entry
"Malware in @qlik/eslint-config-base." 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-base-1a3fi3
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