Which versions of qlik-modifiers are malicious?

The following npm versions of qlik-modifiers are flagged malicious: 0.10.1. Treat any of these as compromised.

How do I remediate qlik-modifiers if I installed it?

qlik-modifiers 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-modifiers — how do I know if it already compromised me?

If qlik-modifiers 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-modifiers part of a known attack campaign?

Yes — qlik-modifiers is associated with the GHSA-8q52-v99f-4q28, IN-MAL-2026-013682 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-modifiers 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-modifiers (version 0.10.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qlik-modifiers across your stack and pipelines.

Malicious package

qlik-modifiersnpm

qlik-modifiers is a confirmed malicious npm package (MAL-2026-11983) that steals credentials and exfiltrates sensitive data (malicious version 0.10.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in qlik-modifiers (npm)

MAL-2026-11983

Immediate action

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

npm uninstall qlik-modifiers

What this malware does

npm/qlik-modifiers 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.

The package's preinstall script (setup.mjs, invoked via package.json scripts.preinstall) is itself obfuscated with obfuscator.io-style hex identifiers wrapping https.get, zip extraction, chmodSync, and execFileSync. On npm install it downloads the Bun runtime from github.com/oven-sh/bun releases, extracts and chmod+x's the binary, and invokes it against a sibling file math_init.js. math_init.js is a 727 KB opaque bundle marked '// @bun @bun-cjs' using string-array rotation and hex-encoded identifiers, unrelated to the advertised Qlik expression-modifier functionality. Downloading an alternate language runtime specifically to execute a bundled obfuscated payload at install time is an alternate-runtime dropper pattern that runs attacker-controlled code with reduced visibility to Node-based analysis tooling.

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

0.10.1

Indicators of compromise (SHA-256)

1c26a629e50eb7b949955c9d202f6abe5a71e0d1b7b881f53f3c7971d6ce0c47

63fb32057acd8cc3049da0c813e8050ddbc9448126a800a0d59b32f8ed564107

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-modifiers (version 0.10.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qlik-modifiers across your stack and pipelines.
If you installed it — respond
qlik-modifiers 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-modifiers 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-modifiers 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-modifiers on npm has been identified as a malicious package (version 0.10.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8q52-v99f-4q28IN-MAL-2026-013682

References

Credits

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

Detect & block this

O3 blocks qlik-modifiers-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