Which versions of react-fontawesome-icons are malicious?

The following npm versions of react-fontawesome-icons are flagged malicious: 1.0.1, 1.0.2, 1.0.4, 1.0.6. Treat any of these as compromised.

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

react-fontawesome-icons is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

react-fontawesome-iconsnpm

react-fontawesome-icons is a confirmed malicious npm package (MAL-2026-12423) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-fontawesome-icons (npm)

MAL-2026-12423

Immediate action

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

npm uninstall react-fontawesome-icons

What this malware does

The package is advertised as a React FontAwesome SVG icon component, but its default-exported Icon component performs unconditional network I/O on every render: an axios GET to http://command.control followed by an axios POST to http://commad.control/404 whose body includes document.cookie and a constructed data object. Any application that renders this component leaks its users' session cookies over plaintext HTTP to an author-hardcoded non-first-party destination unrelated to the package's stated purpose. Surrounding source uses cover-story identifiers and comments (e.g. not_ma_li_ci_ous_at_all, build_the_f_l_a_g, a base64 blob passed to atob, and a comment claiming the icon is harmless) that further indicate deliberate concealment of the exfiltration behavior.

Malicious versions

4 flagged

1.0.11.0.21.0.41.0.6

Indicators of compromise (SHA-256)

06bc9138ae52b505e55664ed2e899a5dba05546a99c9b95622a5295ab68d4102

36a964041c29f69f015fc70f947e1172bd1e8fd92b6292d3014117d4f1c6f191

aef5cf6c4b85c34ea671ef8cdab9298c27bced2231983eb09fa9c9a230a0e86c

2e0b2ce40b563a4df5cb30b6b263d7773c69c318ad994e8146219fae8c6fc6b2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-fontawesome-icons (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-fontawesome-icons across your stack and pipelines.
If you installed it — respond
react-fontawesome-icons is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-fontawesome-icons 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-fontawesome-icons 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-fontawesome-icons on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.4, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014690IN-MAL-2026-014910IN-MAL-2026-014902IN-MAL-2026-014908

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-fontawesome-icons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database