Which versions of @qlik/runtime-module-loader are malicious?

The following npm versions of @qlik/runtime-module-loader are flagged malicious: 1.5.1. Treat any of these as compromised.

How do I remediate @qlik/runtime-module-loader if I installed it?

@qlik/runtime-module-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @qlik/runtime-module-loader — how do I know if it already compromised me?

If @qlik/runtime-module-loader was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @qlik/runtime-module-loader part of a known attack campaign?

Yes — @qlik/runtime-module-loader is associated with the GHSA-j38m-872j-mpmj, IN-MAL-2026-013972 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @qlik/runtime-module-loader across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @qlik/runtime-module-loader (version 1.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @qlik/runtime-module-loader across your stack and pipelines.

Part of a larger attack: @qlik published 28 malicious packages. See the full campaign →

Malicious package

@qlik/runtime-module-loadernpm

@qlik/runtime-module-loader is a confirmed malicious npm package (MAL-2026-11803) that steals credentials and exfiltrates sensitive data (malicious version 1.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @qlik/runtime-module-loader (npm)

MAL-2026-11803

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @qlik/runtime-module-loader

What this malware does

npm/@qlik/runtime-module-loader is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook ("preinstall": "node setup.mjs") that runs on a bare npm install, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations.

@qlik/[email protected] declares a preinstall hook that runs setup.mjs (itself obfuscated with obfuscator.io-style single-letter identifiers). setup.mjs downloads the Bun runtime from github.com/oven-sh/bun releases, chmods it executable, and invokes it against a bundled math_init.js — a 727 KB file containing a rotated string-array (numeric constant array plus a rotator function that shifts the array) and single-letter renamed identifiers, classic string-array obfuscation. The math_init.js filename is unrelated to the package's stated purpose (a module loader), and executing package-shipped code via a freshly-downloaded alternate runtime routes execution outside Node so Node-based install-time scanners do not observe it. Installing the package auto-executes this payload on npm install via the preinstall lifecycle, running attacker-controlled obfuscated code on the installer's machine.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.5.1

Indicators of compromise (SHA-256)

f09f4588fe5bc6e913fd270df870fc2b0812f4d3dcba39a3bdd3d71d99d91a66

f3c75a11f5fbe1f162c4edbe9d0de7a980881136cadf307578aa12c98f0661fb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @qlik/runtime-module-loader (version 1.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @qlik/runtime-module-loader across your stack and pipelines.
If you installed it — respond
@qlik/runtime-module-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @qlik/runtime-module-loader was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @qlik/runtime-module-loader before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @qlik/runtime-module-loader on npm has been identified as a malicious package (version 1.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j38m-872j-mpmjIN-MAL-2026-013972

References

Credits

Aikido Security · finder
Amazon Inspector · finder
SafeDep · finder
Socket Threat Research Team · finder

Detect & block this

O3 blocks @qlik/runtime-module-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database