Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@nebula.js/sn-distributionplotnpm

@nebula.js/sn-distributionplot is a confirmed malicious npm package (MAL-2026-11573) that steals credentials and exfiltrates sensitive data (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nebula.js/sn-distributionplot (npm)

MAL-2026-11573
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nebula.js/sn-distributionplot

What this malware does

npm/@nebula.js/sn-distributionplot 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.

This version of @nebula.js/sn-distributionplot declares preinstall: node setup.mjs in package.json. setup.mjs is an obfuscated loader (renamed _0x... identifiers, per-call string dictionaries) that downloads the Bun runtime from the oven-sh GitHub releases, extracts it to a temp directory, chmods it executable, and then invokes it via execFileSync against a sibling file math_init.js. math_init.js is a 727KB single-line obfuscator.io-style bundle (rotating string array, hex-named identifiers, custom decoder) whose executed contents are not human-inspectable without decoding. Neither setup.mjs nor math_init.js is listed in the package.json files allowlist (which declares only api-specifications, core, core/esm, dist, sn-distributionplot-ext), yet both are shipped in the tarball and run at install time. The bundled dist/sn-distplot.js banner reads v1.0.6 while the package version is 1.0.7, and the legitimate upstream qlik-oss/nebula.js repository has no preinstall script or Bun dependency. The package repackages legitimate Qlik supernova bundle contents while smuggling in an undeclared, obfuscated payload executed under a freshly-downloaded alternate runtime — an alternate-runtime-dropper pattern designed to bypass Node-based scanners at npm install time.

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

Indicators of compromise (SHA-256)

4eef0b505c3023fc6a1165560eff93b449c0254a0164b8d3da7d2a6239d302ef
ddc9d81bf7c09aebb558642ea1fbcc2a066a1cc400fee841d295428990a288f7

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 @nebula.js/sn-distributionplot (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nebula.js/sn-distributionplot across your stack and pipelines.

  2. If you installed it — respond

    @nebula.js/sn-distributionplot 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 @nebula.js/sn-distributionplot 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 @nebula.js/sn-distributionplot 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. @nebula.js/sn-distributionplot on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7hw3-vjh3-29g6IN-MAL-2026-013512

References

Credits

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

Detect & block this

O3 blocks @nebula.js/sn-distributionplot-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

@nebula.js/sn-distributionplot (npm) malicious package — MAL-2026-11573 | O3 Security