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/hitlnpm

@or-sdk/hitl is a confirmed malicious npm package (MAL-2026-11697) that steals credentials and exfiltrates sensitive data (malicious versions 0.41.1, 0.41.2, 0.41.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @or-sdk/hitl (npm)

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

What this malware does

npm/@or-sdk/hitl 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 package declares preinstall: node setup.mjs, which runs automatically on npm install. setup.mjs uses _0x-style identifier obfuscation and downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/<archive>.zip (falling back to a system bun), then invokes it via execFileSync(bunPath, [<pkg>/math_init.js]). The bundled math_init.js is a 727KB @bun @bun-cjs file with heavy obfuscation: a large mixed numeric/string constant array plus a rotator function WV8StW that permutes the array at load. The package's advertised purpose is a HITL REST API SDK, which has no legitimate need for a second JavaScript runtime, no need for a native math_init.js, and no need to run either at install time. The opaque payload is handed to a freshly-downloaded interpreter with no hash or signature verification, and the setup script's obfuscation actively hides the flow. This is an alternate-runtime dropper: a second JS runtime is fetched specifically to execute a sibling file that Node-based scanners typically will not inspect, executing on the installer's machine with the installer's privileges on npm install.

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
0.41.10.41.20.41.3

Indicators of compromise (SHA-256)

16bdd8178a0a061ca763d4749f2f47029667ba25ad4eb4ea955b996eb7807485
0384736d2a333cfdd1f09479a0b03b2a128d571fc987cf25fd96809b9587a422
55bbb62ab2717264234062ad841384999acc9c384c8e3916f3cbbe8ec8cb530d
ee90af5ab1e75089cb66eeeb785df4279664ef53c0b0a22eab57248002044919

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/hitl (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/hitl across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-rvcx-qqp9-jjf3IN-MAL-2026-013823IN-MAL-2026-014135IN-MAL-2026-014025

References

Credits

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

Detect & block this

O3 blocks @or-sdk/hitl-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/hitl (npm) malicious package — MAL-2026-11697 | O3 Security