anhn-clinpm
Advisory published Updated
anhn-cli is a confirmed malicious npm package (MAL-2026-14290) that executes malicious code on install (malicious version 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in anhn-cli (npm)
What this malware does
bin/install/install.js appends a heavily obfuscated top-level IIFE (obfuscator.io-style rotated string array _0x240a/_0x4963 with arithmetic index decoding) after the benign install() helper. The payload queries public Ethereum RPCs and etherscan.io for transactions from the hardcoded sender address 0xa322E5f3..., decodes the transaction to field as an IPv4 address, fetches an XOR-encrypted body from that host, and executes it via eval(prefix+xor(body)) and a detached spawn('node', ['-e',...], {detached:true}).unref(). The package's main entry (bin/index.js) unconditionally requires./install/install, so the IIFE runs whenever the package is required or the CLI is invoked. The attacker controls the fetched payload by publishing new Ethereum transactions from the sender address; there is no version pinning, no signature check, and the destination host rotates on-chain. Decoded strings inside the string array include eth_getBlockByNumber, etherscan.io, eval, and spawn.
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
Malicious packageFind it
Search your lockfiles and build artifacts for anhn-cli (version 1.1.4).
If you installed it — respond
Remove anhn-cli 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.
Did it already run?
If anhn-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks anhn-cli-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.