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

@onereach/pnpm-audit-junitnpm

@onereach/pnpm-audit-junit is a confirmed malicious npm package (MAL-2026-11621) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/pnpm-audit-junit (npm)

MAL-2026-11621
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/pnpm-audit-junit

What this malware does

npm/@onereach/pnpm-audit-junit 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 is obfuscator.io-style minified (control-flow-flattening dispatchers, _0xNNNNNN identifiers) and, at install time, downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<V>/... into a tempdir, chmods it executable, and invokes it via execFileSync against a bundled sibling math_init.js. math_init.js is a 727KB single-line obfuscated bundle (rotating string-array via WV8StW, large mixed literal table) whose behavior is not readable as source. The package's advertised purpose is converting pnpm audit output to JUnit XML, which does not require a second JS runtime — fetching Bun exists to execute a payload that plain Node cannot introspect. Additionally, package.json declares files: ['dist'], but setup.mjs and math_init.js are shipped at the tarball root outside the declared publish surface while still wired into the preinstall lifecycle. The combination of alternate-runtime drop, opaque obfuscated executable payload, mismatched declared files, and a stated purpose that does not require any of this constitutes an install-time remote-code-execution dropper against installers.

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

Indicators of compromise (SHA-256)

6d57b6df99d47ef1d862b7dc25744671c6f5d3e20d171c729f7ffb9870053052
d0b7dee525573f5767540919526c9d4279659914b377153eaf4ced53f7d2275c
18208bf776f351d2c922fbceb94600ab5cce7848b3880e18430db29d06a797aa
2753a29bbf6a7f3930fe833c8b72b93de91aeac5ff63c6718ecd49c592e5b6d2

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

  2. If you installed it — respond

    @onereach/pnpm-audit-junit 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/pnpm-audit-junit 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/pnpm-audit-junit 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/pnpm-audit-junit on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xhrf-6h42-qx33IN-MAL-2026-013711IN-MAL-2026-013746IN-MAL-2026-013874

References

Credits

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

Detect & block this

O3 blocks @onereach/pnpm-audit-junit-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/pnpm-audit-junit (npm) malicious package — MAL-2026-11621 | O3 Security