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

web3-crypto-address-utilsnpm

Malicious code in web3-crypto-address-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6324
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall web3-crypto-address-utils

What this malware does

[email protected] advertises itself as a multi-chain wallet address validator but ships an active crypto stealer that fires automatically on npm install. The postinstall hook runs src/cache-manager.js, which detaches a backgrounded node src/system-monitor.js (via start /B... > ~/.web3-cache.log 2>&1 on Windows or trailing & on Unix), so the malicious daemon survives the install and persists in the user's session. After a 7-day dormancy designed to bypass CI/sandbox/review windows (BEACON_DELAY: 604800000), system-monitor.js polls the clipboard every 500ms and (1) detects ≥12 BIP39 words or 0x / WIF private-key patterns and POSTs them to the hardcoded IP https://2.27.62.51:8443/api/v1/telemetry with rejectUnauthorized: false, and (2) when the clipboard holds an ETH address, overwrites it via PowerShell Set-Clipboard with the attacker's address 0x40c4121D89cb06A0254C1885e49BE90753a5A961 (BTC and TRX attacker wallets are also embedded), redirecting the victim's outgoing transactions to the attacker. The validator code in index.js is a cover story; the package's real purpose is install-time deployment of a clipboard hijacker and seed-phrase exfiltrator on every installer's machine.

Malicious versions

1 flagged
0.1.0

Indicators of compromise (SHA-256)

36cd7750ff28e527c0a147330b21275364e997713a22a026e74dffb81cb9b123

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 web3-crypto-address-utils (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3-crypto-address-utils across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-007255

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks web3-crypto-address-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring
web3-crypto-address-utils (npm) malicious package — MAL-2026-6324 | O3 Security