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

@nebula.js/sn-shapenpm

@nebula.js/sn-shape is a confirmed malicious npm package (MAL-2026-11580) 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 @nebula.js/sn-shape (npm)

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

What this malware does

npm/@nebula.js/sn-shape 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 1.5.1 tarball adds two files at the tarball root that are not present in the package's declared files manifest (dist, sn-shape-ext, api-spec/spec.json, core): setup.mjs and a 727 KB obfuscated Bun-compiled bundle math_init.js. package.json declares scripts.preinstall: "node setup.mjs". On npm install, setup.mjs checks for a local bun binary and, if absent, downloads a Bun runtime zip from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/..., extracts and chmods the binary, then invokes it via execFileSync(bunPath, [join(D, 'math_init.js')], { stdio: 'inherit', cwd: D }). math_init.js carries a // @bun @bun-cjs header and standard string-array/rotation obfuscation (function WV8StW(a,b,c){for(c=0;c<b;c++)a.push(a.shift());return a}, hundreds of hex-named identifiers). The package is published as a Qlik nebula.js shape-chart extension and has no documented reason to fetch an alternate language runtime at install time or to execute a bundled obfuscated program under it. The combination of an undeclared install-time payload, download of a second runtime to evade Node-based scanning, and execution of an obfuscated blob is the alternate-runtime-dropper pattern and gives whoever published this version arbitrary code execution on the installer's host 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.5.1

Indicators of compromise (SHA-256)

c0655e7b5866832b04d8ac2c5f3841442103d114c21c5ad3cfc96629ab81bb81
1c835b7535b2fb13d56ec4f1d2bec7bc1b6b5e738fe76330a4a25a136d96b8ca

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-shape (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 @nebula.js/sn-shape across your stack and pipelines.

  2. If you installed it — respond

    @nebula.js/sn-shape 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-shape 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-shape 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-shape 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-7gfj-r25v-v6v2IN-MAL-2026-013504

References

Credits

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

Detect & block this

O3 blocks @nebula.js/sn-shape-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-shape (npm) malicious package — MAL-2026-11580 | O3 Security