crypto-hashernpm
crypto-hasher is a confirmed malicious npm package (MAL-2026-10666) that steals credentials and exfiltrates sensitive data (malicious versions 3.1.2, 3.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in crypto-hasher (npm)
What this malware does
[email protected] impersonates the hash-wasm library. Its main entrypoint (dist/index.umd.js) injects code into the WASM Interface update() method so that any consumer hashing data containing the trigger string 'alicebob100' silently spawns a detached node dist/hasher.umd.min.js alicebob100 child process. The spawned dist/hasher.umd.min.js connects to Ethereum Sepolia RPC endpoints (Infura, Alchemy) with base64-obfuscated URLs, reads encrypted material and a password from a smart contract via ABI methods (getCwPrivatePublic, getSPubKey, getPWD, getTData1, setCPubKey), performs X25519 ECDH against a hardcoded peer public key followed by PBKDF2/AES-GCM decryption to recover a wallet private key, and exfiltrates host reconnaissance (platform, release, arch, hostname, cpus, memory, uptime) to Slack (chat.postMessage with a hardcoded Bearer token and channel id) and Telegram (api.telegram.org/bot<token>/sendMessage with a hardcoded chat id). A second component, dist/hmac.min.js, is spawned with a derived key and polls Slack conversations.history every 10 seconds; JSON chunk messages posted by a specific operator user id are reassembled, AES-GCM/PBKDF2-decrypted, written to disk, chmod 0755, and executed under the installer's Node runtime — a persistent remote code execution backdoor. An 'exitexitexit' command deletes hasher.umd.min.js, hmac.min.js, and edits LICENSE (splice at line 355) as anti-forensics. Destinations, tokens, and the peer public key are hidden with obfuscator.io-style string-array rotation and base64 wrapping.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crypto-hasher (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crypto-hasher across your stack and pipelines.
If you installed it — respond
crypto-hasher 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.
Did it already run?
If crypto-hasher 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.
How O3 protects you
O3 blocks crypto-hasher 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks crypto-hasher-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.