Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @qlik published 28 malicious packages. See the full campaign →
Malicious package

@qlik/design-tokensnpm

@qlik/design-tokens is a confirmed malicious npm package (MAL-2026-11787) that steals credentials and exfiltrates sensitive data (malicious version 1.3.13). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @qlik/design-tokens (npm)

MAL-2026-11787
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @qlik/design-tokens

What this malware does

npm/@qlik/design-tokens 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 declares a preinstall script (node setup.mjs) that runs automatically on npm install. setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip, extracts and chmods the binary executable, then invokes it via execFileSync against a bundled 727KB sibling file math_init.js. math_init.js is heavily obfuscated (obfuscator-style hex identifiers _0x488df8, shuffled string-array rotation dispatcher, char-code decoding tables, // @bun @bun-cjs header) and is not consumed as a library by the package's declared design-tokens purpose (CSS variables / JSON). setup.mjs itself also contains obfuscator-style identifiers. The Bun release tag is derived from the package's own version string V = "1.3.13" rather than a pinned runtime version, coupling the fetched external artifact to the publisher's package version. Fetching an alternate language runtime specifically to execute an opaque obfuscated bundled payload at install time is the alternate-runtime-dropper pattern; a design-tokens library has no functional need for a second language runtime or an obfuscated 727KB executable blob. Installing this version causes arbitrary code contained in math_init.js to run on the installer's host under the downloaded Bun binary, bypassing Node-based inspection.

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.3.13

Indicators of compromise (SHA-256)

8874611a7a69c6be6802f46374304d8adfff16c74473aeb9527a32176be273cd
0509e4c9bf359db03d8552c003dd7eaf39f7f43fc5b169e8cbff7bb651312e47

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @qlik/design-tokens 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.

  3. Did it already run?

    If @qlik/design-tokens 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.

  4. How O3 protects you

    O3 blocks @qlik/design-tokens 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/design-tokens on npm has been identified as a malicious package (version 1.3.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p4mv-wfgp-356cIN-MAL-2026-013975

References

Credits

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

Detect & block this

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

Explore

@qlik/design-tokens (npm) malicious package — MAL-2026-11787 | O3 Security