Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@arv-bedrock/auth-sso-backendnpm

@arv-bedrock/auth-sso-backend is a confirmed malicious npm package (MAL-2026-11556) that steals credentials and exfiltrates sensitive data (malicious versions 1.7.1, 1.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @arv-bedrock/auth-sso-backend (npm)

MAL-2026-11556
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @arv-bedrock/auth-sso-backend

What this malware does

npm/@arv-bedrock/auth-sso-backend 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 (v1.3.13) from GitHub, extracts it to a temporary directory, chmods it executable, and invokes it via execFileSync(bunPath, [math_init.js], {cwd:D}) to run a package-local file math_init.js. math_init.js is a 727KB single-line heavily obfuscated bundle (header // @bun @bun-cjs, hex-name identifiers, a multi-thousand-entry mixed literal array driving a rotating string-array decoder function WV8StW). The obfuscated payload is not referenced from the declared library entrypoint (dist/cjs/index.js) and is not listed in package.json.files (which allows only dist/**/*); it exists in the tarball solely to be executed by the preinstall dropper. Package metadata is placeholder (author: "", description: "") and the README contains only pipeline-trigger notes, with no relation to the advertised SSO-backend purpose. Executing under a freshly downloaded alternate runtime bypasses Node-based install-time monitoring, and the opaque payload's behavior cannot be inspected by the installer.

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

2 flagged
1.7.11.7.2

Indicators of compromise (SHA-256)

f9e82cedd0e05f2fc43cf2ca91c78df40024cc13a695fba8f616c2cacd4370e3
d79ed18957dd02747aaf0c294be62dfa7c4d69ca7ef7ba8b736c171c9d31b8f7
0e368d468389d15efb3701f793408a6d569bb8aa027513fed45222df718ebd81

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 @arv-bedrock/auth-sso-backend (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @arv-bedrock/auth-sso-backend across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-mh3h-7fpv-657fIN-MAL-2026-013601IN-MAL-2026-013602

References

Credits

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

Detect & block this

O3 blocks @arv-bedrock/auth-sso-backend-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

@arv-bedrock/auth-sso-backend (npm) malicious package — MAL-2026-11556 | O3 Security