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

ethers-abstract-signernpm

Malicious code in ethers-abstract-signer (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3760
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ethers-abstract-signer

What this malware does

On npm install, the package's postinstall hook spawns a Node one-liner that uses child_process.exec to curl/wget https://gist.githubusercontent.com/guellemilb/631fb6348967d9d475125edf67048c0e/raw/build_utils.py and pipe the response directly into python3 (falling back to node and wget variants), then eval()s the exec callback's stdout. The URL is a mutable personal GitHub Gist, not tied to the package publisher, with no version pin and no integrity check, so the Gist owner can swap in arbitrary code at any time and it will execute on every installer's machine. The package's advertised purpose is an 'ethers development aid for Solidity projects', and it impersonates the ethers.js AbstractSigner API, but index.js is effectively empty (module.exports = {}) — the only functional effect of installing the package is the remote-code fetch and execute. The name mimics the legitimate ethers ecosystem, increasing the chance of accidental installation by developers searching for an AbstractSigner helper.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

4030fc941019f32214ada9d3dc3db7fccf1cd6732c6c0af57ce4b8993a7dc018
e17d355d974f842bc8db3219ce3f1dc6e643f2a5e1ba8dd0b38a404a8f96e9a8
2cfbc22e6c81d171169227dafad300ab1ebd6624a2dd09991a4b8c47fbcc65b7

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ethers-abstract-signer (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 ethers-abstract-signer across your stack and pipelines.

  2. If you installed it — respond

    ethers-abstract-signer is a typosquat — you almost certainly intended a legitimately-named package. Remove ethers-abstract-signer, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If ethers-abstract-signer 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 ethers-abstract-signer 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. ethers-abstract-signer 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-002811IN-MAL-2026-002712GHSA-2f7m-g9qw-8288

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ethers-abstract-signer-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.

ethers-abstract-signer (npm) malicious package — MAL-2026-3760 | O3 Security