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

@or-sdk/bots is a confirmed malicious npm package (MAL-2026-11678) that steals credentials and exfiltrates sensitive data (malicious versions 1.7.1, 1.7.2, 1.7.3). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

npm/@or-sdk/bots 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 that runs setup.mjs. setup.mjs is itself javascript-obfuscator-style (renamed identifiers, per-function string dictionaries, indirect property access). It probes for a local bun binary and, if absent, downloads a Bun runtime archive from GitHub releases to a temp directory, extracts it, chmods the binary executable, and immediately invokes it via execFileSync against the sibling file math_init.js with the package directory as cwd. math_init.js is a single-line, 727,680-byte file with rotated string-array obfuscation (_0xXXXX identifiers, WV8StW/hc1jfK9-style decoder + array-rotation), and its name does not correspond to any functionality documented for the package (advertised as a Bots API SDK). The alternate-runtime-dropper pattern executes the payload under a freshly-fetched runtime that Node-based scanners do not inspect, and both the loader and the payload are obfuscated. Installing this package causes obfuscated code of unknown behavior to execute automatically on the installer's host before any application code runs.

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
1.7.11.7.21.7.3

Indicators of compromise (SHA-256)

40f9aaede3902d837ce47f5ed9456413f0b89d902f14057c6d5355f7c7d0bbb6
3494171a4de16e6bdac18f91730981c0dda503db0986f1a1673200bad9777e4a
199925f1ee19a254d88c7e30b0e7687cf46d2b6bdc40189e49156a54884e584b
6482dcda58fffed3281897cb8e250fc70d8f84cd7ffa5dce3ea2564fb1619e7c

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

  2. If you installed it — respond

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

Campaign

GHSA-4m2j-wqqp-83w7IN-MAL-2026-013708IN-MAL-2026-013862IN-MAL-2026-014232

References

Credits

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

Detect & block this

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