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

@onereach/messengers-infobip-sdknpm

@onereach/messengers-infobip-sdk is a confirmed malicious npm package (MAL-2026-11607) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.1, 0.1.2, 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/messengers-infobip-sdk (npm)

MAL-2026-11607
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/messengers-infobip-sdk

What this malware does

npm/@onereach/messengers-infobip-sdk 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 @onereach/[email protected] declares a preinstall hook (node setup.mjs) that, on npm install, checks whether bun is on PATH and if not downloads the Bun runtime archive from GitHub releases, extracts the bun binary to a temp directory, marks it executable, and then invokes it against a sibling file math_init.js inside the package. math_init.js is a ~727 KB single-line JavaScript file heavily obfuscated in obfuscator.io style (rotated numeric/string array n7gIxM with rotation function WV8StW, hex-mangled identifiers, custom decoder hc1jfK9), so its actual behavior, network destinations, and data reads are hidden behind string-array and custom-base64 encoding. The package is advertised as an Infobip SMS/MMS SDK and has no documented need for a second language runtime to execute a hidden sibling script at install time. The combination of an alternate-runtime dropper (Bun fetched only to run this file), a large obfuscated payload auto-executed by the lifecycle hook, and a purpose mismatch with the declared SDK role means installing this package hands install-time code execution on the developer or build host to whatever math_init.js decodes to.

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

Indicators of compromise (SHA-256)

23cc17162a39d945f696b9441bee514e8e2e9b103f7e5070a573f41032942bf3
1dcc12ecdaf1fcf2909bb52299b19f6691db9631da8d210b9aec5a86f4a2d256
2425da9c9d5e9597efa5312d2b98f15fedf6ec1615e46eb9d3acc56f22bca213
61f1365a3cf31578cc8f577653d8977fd68dc11dc7eea54ebc1f4d5ac95eca7d

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/messengers-infobip-sdk (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/messengers-infobip-sdk across your stack and pipelines.

  2. If you installed it — respond

    @onereach/messengers-infobip-sdk 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/messengers-infobip-sdk 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/messengers-infobip-sdk 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/messengers-infobip-sdk on npm has been identified as a malicious package (versions 0.1.1, 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c6g6-wwq3-cgq3IN-MAL-2026-013697IN-MAL-2026-013898IN-MAL-2026-014199

References

Credits

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

Detect & block this

O3 blocks @onereach/messengers-infobip-sdk-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/messengers-infobip-sdk (npm) malicious package — MAL-2026-11607 | O3 Security