Which versions of @or-sdk/identifiers are malicious?

The following npm versions of @or-sdk/identifiers are flagged malicious: 0.27.6, 0.27.7, 0.27.8. Treat any of these as compromised.

How do I remediate @or-sdk/identifiers if I installed it?

@or-sdk/identifiers 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.

I already installed @or-sdk/identifiers — how do I know if it already compromised me?

If @or-sdk/identifiers 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.

Is @or-sdk/identifiers part of a known attack campaign?

Yes — @or-sdk/identifiers is associated with the GHSA-rx3p-hh6j-4c47, IN-MAL-2026-013771, IN-MAL-2026-014139, IN-MAL-2026-014017 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @or-sdk/identifiers across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @or-sdk/identifiers (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/identifiers across your stack and pipelines.

Part of a larger attack: @or-sdk published 74 malicious packages. See the full campaign →

Malicious package

@or-sdk/identifiersnpm

@or-sdk/identifiers is a confirmed malicious npm package (MAL-2026-11698) that steals credentials and exfiltrates sensitive data (malicious versions 0.27.6, 0.27.7, 0.27.8). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-11698

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @or-sdk/identifiers

What this malware does

npm/@or-sdk/identifiers 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 a preinstall hook (node setup.mjs) that downloads the Bun runtime from github.com/oven-sh/bun releases (bun-v1.3.13/<platform>.zip) into a temp directory, extracts it, chmods it executable, and then invokes it via execFileSync against a sibling file math_init.js. If a local bun is already present it is used directly. math_init.js is a ~727 KB single-line // @bun @bun-cjs bundle containing string-array-rotation obfuscation with an alphabet-substitution decoder (hc1jfK9, WV8StW rotator, MmgoCP/n7gIxM tables). The package advertises itself as an identifiers SDK, a purpose unrelated to fetching an alternate language runtime or executing a heavily obfuscated ~727 KB payload at install time. Downloading an alternate runtime specifically to execute an obfuscated local script evades Node-based install-time scanners and matches the alternate-runtime-dropper pattern; the obfuscated payload's actual behavior is intentionally hidden from static review.

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

Indicators of compromise (SHA-256)

75326c1bb71e6a912f81becb290cf37536d4a193d22bc448eca76c9dabec6372

79c570f98378a46da05e351891d0a9df30d1e1ab241fdbdf9f22e0d2545f1c05

dfd9e1cb5cadefa94ca4e767c2f10273c9f22e255d054ed3ddb589b828a01261

e14be760600e0b50859a91ed1563c228b4ae19925aa144b1b475ef95c835f0d1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @or-sdk/identifiers (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/identifiers across your stack and pipelines.
If you installed it — respond
@or-sdk/identifiers 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.
Did it already run?
If @or-sdk/identifiers 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.
How O3 protects you
O3 blocks @or-sdk/identifiers 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/identifiers on npm has been identified as a malicious package (versions 0.27.6, 0.27.7, 0.27.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rx3p-hh6j-4c47IN-MAL-2026-013771IN-MAL-2026-014139IN-MAL-2026-014017

References

Credits

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

Detect & block this

O3 blocks @or-sdk/identifiers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database