Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in qlik-modifiers

Malware was discovered in the npm package qlik-modifiers. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with qlik-modifiers installed or running
Ecosystems
Attack vectors
Affected entities
  • qlik-modifiersnpm package

The npm package qlik-modifiers was found to contain malware. According to the GitHub Advisory (GHSA-8q52-v99f-4q28), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system compromise."

Indicators of compromise

Packages
  • qlik-modifiers

Remediation

  • Immediately isolate any system with qlik-modifiers installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the qlik-modifiers package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system rebuild if sensitive data or systems were compromised

Sources

  1. GitHub Advisory GHSA-8q52-v99f-4q28 · GitHub Advisory Database

Cite this entry

"Malware in qlik-modifiers." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-qlik-modifiers-1pieg6

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in fetch-runtime

    Malware was discovered in the npm package fetch-runtime. Any system 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
  2. resolvedcritical

    Malicious code in ghazaly (npm)

    The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.

    npmCompromised packageDependency confusion
  3. containedcritical

    Malicious code in base65-13x (npm)

    base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.

    npmCompromised package
  4. containedcritical

    Malicious code in kit-vim-map (npm)

    The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.

    npmCompromised packageMalicious commit