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

@or-sdk/data-hub-svcnpm

@or-sdk/data-hub-svc is a confirmed malicious npm package (MAL-2026-11686) that steals credentials and exfiltrates sensitive data (malicious versions 2.3.5, 2.3.6, 2.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @or-sdk/data-hub-svc (npm)

MAL-2026-11686
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @or-sdk/data-hub-svc

What this malware does

npm/@or-sdk/data-hub-svc 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.json declares a preinstall hook node setup.mjs. setup.mjs uses hex-mangled _0x... identifiers to download a platform-specific Bun runtime zip from github.com/oven-sh/bun/releases (bun-v1.3.13), extracts it to an OS temporary directory, chmods the binary executable, and invokes it against a sibling file math_init.js via execFileSync(bunPath, ['math_init.js'], { stdio: 'inherit' }). math_init.js is a ~727KB single-line // @bun @bun-cjs bundle with hex-mangled identifiers, a large rotated string/number constant array, and a string-array shuffle routine (WV8StW) — the canonical obfuscator.io string-array pattern. The bundled payload is only reachable through the alternate Bun runtime dropped at install time, bypassing Node-based inspection. The package advertises itself as a data-hub SDK; that purpose does not require fetching a second language runtime or executing an opaque compiled blob. Installing this package on any platform automatically fetches an external binary and executes attacker-controlled obfuscated code on the installer host.

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

3 flagged
2.3.52.3.62.3.7

Indicators of compromise (SHA-256)

5b716d5b6153f595420e47ebf7bc938c2578476f8763b702496b827139c17ad5
46e3cea01ce757a1db08a29184f26596d373dc78943b97447a7e1028877ade66
56ba4d39d78074c1a4bc49e70bf107240a35138d8f83566fe017cc23cd8bdb0c
ca56df0139c6aa5185e818e877439efafd80bd13cf7a3cf2521c4269d733f5e3

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 @or-sdk/data-hub-svc (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @or-sdk/data-hub-svc across your stack and pipelines.

  2. If you installed it — respond

    @or-sdk/data-hub-svc 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 @or-sdk/data-hub-svc 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 @or-sdk/data-hub-svc 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. @or-sdk/data-hub-svc on npm has been identified as a malicious package (versions 2.3.5, 2.3.6, 2.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hj82-vqh6-4cjpIN-MAL-2026-014049IN-MAL-2026-013818IN-MAL-2026-014163

References

Credits

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

Detect & block this

O3 blocks @or-sdk/data-hub-svc-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

@or-sdk/data-hub-svc (npm) malicious package — MAL-2026-11686 | O3 Security