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

@nebula.js/sn-nav-menunpm

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

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

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

What this malware does

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

Package publishes under the @nebula.js scope (claiming author 'QlikTech International AB') and advertises itself as a Qlik Sense navigation menu extension, but its package.json declares a preinstall hook node setup.mjs. setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip to a temp directory, chmods it executable, and then execFileSyncs the Bun binary against a sibling file math_init.js. math_init.js is a 727KB // @bun @bun-cjs compiled blob with a rotated numeric constant table and hex-mangled identifiers (_0x...), unrelated to the package's stated Qlik navigation-menu purpose (whose React/MUI code lives in dist/). The payload only executes under the freshly downloaded second runtime, so its contents cannot be reviewed by normal Node-based inspection and it runs automatically on npm install. The scope/author claim to a legitimate Qlik ecosystem name combined with an obfuscated alternate-runtime dropper is the impersonation-plus-install-time-RCE shape.

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

Indicators of compromise (SHA-256)

74f179735798360b3fdeeaa137914330a82656634dcd3d5a516411e253cd8adf
8e1fb5e0b6488de0d1f71b298361cd50b630c7a6a6c1c16cc271490f61b5c0eb

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

  2. If you installed it — respond

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

Campaign

GHSA-252m-vjpw-497vIN-MAL-2026-013572

References

Credits

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

Detect & block this

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