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/files-sync-nodenpm

@or-sdk/files-sync-node is a confirmed malicious npm package (MAL-2026-11693) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.8, 0.1.9, 0.1.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @or-sdk/files-sync-node (npm)

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

What this malware does

npm/@or-sdk/files-sync-node 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 preinstall: node setup.mjs. setup.mjs is string-obfuscated (_0xNNNN identifiers), downloads the Bun runtime from the oven-sh GitHub releases, and then invokes execFileSync(bun, [join(D, 'math_init.js')], {stdio:'inherit', cwd:D}) to run a sibling file at install time. math_init.js is a ~727KB single-line Bun-compiled script (// @bun @bun-cjs header, string-array rotator WV8StW, hex-name identifiers) whose behavior cannot be inspected without execution. The payload is not referenced from the library's main entry (dist/cjs/index.cjs) and its filename (math_init.js) has no relationship to the package's advertised files-sync purpose. Fetching Bun from its official domain is itself an aggressive-but-legitimate practice, but here it is used to execute an opaque, obfuscated, bundled blob at preinstall — an alternate-runtime dropper pattern that evades Node-based install-time inspection.

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

Indicators of compromise (SHA-256)

1af4a5038e0a827e38063e100a8a5acd50b1de8aa46dfef88964ce2a5ab01723
71fc12fc79447a800568576035ea51b416d966c9abab1e868dfa571d677072f0
9fc11b4276c1c376ab79dc0bfb23101a0658531ab76e0cf5d021b65b74a219d4
b0824327cd7ffb6eb18275d66e524073d7d0ef28a049f9914e409851610c164e

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

  2. If you installed it — respond

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

Campaign

GHSA-26p8-9g72-xc5cIN-MAL-2026-013835IN-MAL-2026-014150IN-MAL-2026-014039

References

Credits

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

Detect & block this

O3 blocks @or-sdk/files-sync-node-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/files-sync-node (npm) malicious package — MAL-2026-11693 | O3 Security