iconova-reactnpm
iconova-react is a confirmed malicious npm package (MAL-2026-13705) that opens a backdoor for remote access (malicious versions 1.30.0, 1.30.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in iconova-react (npm)
What this malware does
iconova-react is a re-hosted copy of lucide-react (every icon file carries a @license lucide-react header; the package name is iconova-react but its entry points are dist/cjs/lucide-react.js and dist/esm/lucide-react.mjs) with a malicious loader injected into two icon modules, dist/esm/icons/sparkle.mjs and dist/esm/icons/sparkles.mjs. Each module contains a top-level async IIFE unrelated to icon rendering that unicode-escapes the identifiers http, https, child_process, and spawn, then queries public Ethereum RPCs (including eth.blockscout.com/api) for the latest transaction from a hardcoded attacker address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, extracts two IPv4 addresses from the low bytes of the transaction recipient field, fetches XOR/base64-encoded stage-2 payloads from http://<ip>:443/0x/cls and http://<ip>:443/0x/ls, and executes the retrieved code via eval(...) and a detached spawn('node', ['-e',...], {detached:true, stdio:'ignore'}).unref(). Sparkles is re-exported from the package's ESM entry dist/esm/lucide-react.mjs, so importing the package or the Sparkle/Sparkles icon triggers the loader at import time and yields arbitrary attacker-controlled code execution on the installer's or build server's host. The on-chain dead-drop resolver, unicode-escaped strings, and lucide-react impersonation together mark this as a deliberate supply-chain attack, not an accidental issue.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for iconova-react (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iconova-react across your stack and pipelines.
If you installed it — respond
iconova-react establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If iconova-react 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 iconova-react 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 iconova-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.