Which versions of iconova-react are malicious?

The following npm versions of iconova-react are flagged malicious: 1.30.0, 1.30.1. Treat any of these as compromised.

How do I remediate iconova-react if I installed it?

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.

I already installed iconova-react — how do I know if it already compromised me?

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.

Is iconova-react part of a known attack campaign?

Yes — iconova-react is associated with the IN-MAL-2026-017258, IN-MAL-2026-017259 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find iconova-react across my projects, lockfiles, and CI pipelines?

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.

Malicious package

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)

MAL-2026-13705

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall iconova-react

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.

Malicious versions

2 flagged

1.30.01.30.1

Indicators of compromise (SHA-256)

392b2a3a1fac48d18cfd126d3b667f4f91c2992f34bdf4df313f5bd73f33241d

4590534a7b05eb30959d9422e2ea700fb525b66b357a62f7ba1795caba4ad799

Detection & response playbook

Backdoor / remote access

Find 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

No. iconova-react on npm has been identified as a malicious package (versions 1.30.0, 1.30.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017258IN-MAL-2026-017259

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database