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

eth-batchernpm

eth-batcher is a confirmed malicious npm package (MAL-2026-14208) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-batcher (npm)

MAL-2026-14208
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eth-batcher

What this malware does

index.js is a verbatim copy of an unrelated Mongoose LeanHooks Plugin with a ~149 KB obfuscated Function(...) payload concatenated onto the module.exports line. On require(), the payload constructs and executes code decoded from a hex byte table via an XOR/rotation decoder. The advertised purpose in package.json (Ethereum JSON-RPC batching) does not match the shipped code, which contains no Ethereum or Web3 logic — the mismatched benign source acts as a cover for the appended dropper. Any process that imports this package executes the decoded payload at load time.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

e2a725b819260b649f04c27142a0c6e5d219304f6ab038f8717533c2b3416599

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-batcher (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-batcher across your stack and pipelines.

  2. If you installed it — respond

    Remove eth-batcher from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If eth-batcher 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 eth-batcher 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. eth-batcher on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018299

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks eth-batcher-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

eth-batcher (npm) malicious package — MAL-2026-14208 | O3 Security