Which versions of react-icons-svgo are malicious?

The following npm versions of react-icons-svgo are flagged malicious: 1.0.0, 1.5.3, 1.5.4. Treat any of these as compromised.

How do I remediate react-icons-svgo if I installed it?

react-icons-svgo is a typosquat — you almost certainly intended a legitimately-named package. Remove react-icons-svgo, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If react-icons-svgo 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 react-icons-svgo part of a known attack campaign?

Yes — react-icons-svgo is associated with the IN-MAL-2026-010304, IN-MAL-2026-010306, IN-MAL-2026-010305 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 react-icons-svgo 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 react-icons-svgo (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-icons-svgo across your stack and pipelines.

Malicious package

react-icons-svgonpm

Malicious code in react-icons-svgo (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10482

Immediate action

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

npm uninstall react-icons-svgo

What this malware does

index.js stores base64-encoded literals (svgValidateKey, svgValidatePattern) that decode to the shell command npm install rollup-plugin-polyfill-handler --no-save --silent --no-audit --no-fund and to the module name rollup-plugin-polyfill-handler. When the package's advertised API (getPlugin/setPlugin, or any SVG validation path via ValidateSvgModule/ValidateSvgModuleB) is invoked, the code atob-decodes those literals, spawns the install command (suppressing output via --silent --no-audit --no-fund and skipping persistence via --no-save), then require()s the decoded module name and immediately invokes its exported getPlugin(). The fetched package is undeclared in dependencies, its name is hidden behind base64, and its contents are fully controlled by a third-party publisher who can change them at any time — yielding arbitrary remote code execution in the installer's Node process on first use of the advertised SVG utilities. The package name react-icons-svgo further impersonates the popular react-icons and svgo ecosystems while shipping no real functionality beyond a thin CDN helper plus this covert install/require channel.

Malicious versions

3 flagged

1.0.01.5.31.5.4

Indicators of compromise (SHA-256)

40365f843366f9cd2c80f313e99cc021df31c8f80c9813012277617e3fe4c230

5625dd5cae598aa066b4b6f1b5708134da0b3f0907805c0cb3f6dfefefb32430

d0ccdc7a601182ae60a4f75d72cb54aef12fbe94cb209625f6f1c9be47b12096

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-icons-svgo (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-icons-svgo across your stack and pipelines.
If you installed it — respond
react-icons-svgo is a typosquat — you almost certainly intended a legitimately-named package. Remove react-icons-svgo, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-icons-svgo 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 react-icons-svgo 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. react-icons-svgo on npm has been identified as a malicious package (versions 1.0.0, 1.5.3, 1.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010304IN-MAL-2026-010306IN-MAL-2026-010305

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-icons-svgo-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.

Malware detection Runtime egress monitoring