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

@onereach/salesforce-miaw-clientnpm

@onereach/salesforce-miaw-client is a confirmed malicious npm package (MAL-2026-11627) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.3, 0.0.4, 0.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/salesforce-miaw-client (npm)

MAL-2026-11627
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/salesforce-miaw-client

What this malware does

npm/@onereach/salesforce-miaw-client 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 scripts.preinstall = 'node setup.mjs'. setup.mjs uses obfuscated _0x... identifiers and, on npm install, downloads a Bun runtime archive from github.com/oven-sh/bun releases into a temporary directory, extracts and chmods it, then invokes the dropped Bun binary against a sibling file math_init.js at the package root. math_init.js is a ~727KB Bun-compiled (// @bun @bun-cjs) bundle with obfuscator.io-style string-array + rotate obfuscation (function WV8StW rotating a ~1000-entry mixed number/string array, mangled identifiers like MmgoCP, etDiOOB, JqTtnbZ). The name math_init.js has no relation to the advertised Salesforce Messaging-for-In-App-and-Web HTTP client purpose. package.json declares files: ["dist"], yet setup.mjs and the 727KB math_init.js are shipped at the tarball root outside that allowlist, so the payload is not surfaced in the declared manifest and is wired in only through the preinstall lifecycle hook. Executing the payload under Bun places it outside Node's tooling visibility, defeating Node-based supply-chain and runtime scanners. The combination — install-time fetch of a second language runtime, execution of a heavily obfuscated bundle unrelated to the package's stated purpose, and payload smuggling outside the declared files list — is arbitrary code execution on any host running npm install on this version.

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

Indicators of compromise (SHA-256)

b1fb559d97bebc677040ca042a431fce92863b38b60c5ffe64f9181b28a764bd
723a34499e3f75cf2cdcb24e22be99fb8f35b18b97681b3308f88fdfc166bebd
df5aaceb2f852a1b48658a1b698ef2bfa9c9acd29136ed2fbb94ae4e3896968c
46ad79bade066a3605882d23b0c5ef2cd6295a67abb3b087c0c07eba3c623343

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 @onereach/salesforce-miaw-client (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @onereach/salesforce-miaw-client across your stack and pipelines.

  2. If you installed it — respond

    @onereach/salesforce-miaw-client 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 @onereach/salesforce-miaw-client 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 @onereach/salesforce-miaw-client 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. @onereach/salesforce-miaw-client on npm has been identified as a malicious package (versions 0.0.3, 0.0.4, 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-29f9-2vff-42c7IN-MAL-2026-013709IN-MAL-2026-013641IN-MAL-2026-013752

References

Credits

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

Detect & block this

O3 blocks @onereach/salesforce-miaw-client-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

@onereach/salesforce-miaw-client (npm) malicious package — MAL-2026-11627 | O3 Security