Which versions of sn-listbox are malicious?

The following npm versions of sn-listbox are flagged malicious: 0.3.3. Treat any of these as compromised.

How do I remediate sn-listbox if I installed it?

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

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

Yes — sn-listbox is associated with the GHSA-hr73-rrjg-2v2g, IN-MAL-2026-013468 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 sn-listbox 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 sn-listbox (version 0.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sn-listbox across your stack and pipelines.

Malicious package

sn-listboxnpm

sn-listbox is a confirmed malicious npm package (MAL-2026-11987) that steals credentials and exfiltrates sensitive data (malicious version 0.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sn-listbox (npm)

MAL-2026-11987

Immediate action

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

npm uninstall sn-listbox

What this malware does

npm/sn-listbox 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.

[email protected] is an unscoped package impersonating QlikTech's @nebula.js/sn-listbox supernova. The dist/sn-listbox.js main bundle is a verbatim copy of the legitimate Qlik sn-listbox v0.3.1 bundle, used as cover. package.json declares "preinstall": "node setup.mjs". setup.mjs downloads the Bun runtime from github.com/oven-sh/bun/releases/download/bun-v1.3.13/, extracts it, chmods it executable, and invokes it with the bundled math_init.js as its argument. math_init.js is a 727 KB single-line obfuscated blob (shifted string-array with a custom decoder and with-statement lookups that defeat standard AST parsers) shipped at the package root, unrelated to the advertised Qlik listbox purpose and not present in the upstream project. On npm install, the preinstall hook executes this obfuscated payload under a separately-fetched runtime, bypassing Node's normal module graph.

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

Indicators of compromise (SHA-256)

98d25c0e163209cb158349d2d7396bd7da0f5f081e7582c49ce663750cbe350e

a35e9c41b95b8bf55987ee158097b5639b6c016d9fd21d6b27dc5ba595833a26

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

Campaign

GHSA-hr73-rrjg-2v2gIN-MAL-2026-013468

References

Credits

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

Detect & block this

O3 blocks sn-listbox-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