anhn-clinpm
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for anhn-cli (version 1.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anhn-cli across your stack and pipelines.
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 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 anhn-cli 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 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.