Which versions of react-icons-loader are malicious?

The following npm versions of react-icons-loader are flagged malicious: 25.9.29. Treat any of these as compromised.

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

Remove react-icons-loader 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.

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

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

Yes — react-icons-loader is associated with the GHSA-69v9-mcpc-9hgm, RLMA-2025-05497, RLUA-2025-05926 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-loader 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-loader (version 25.9.29). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-icons-loader across your stack and pipelines.

Malicious package

react-icons-loadernpm

react-icons-loader is a confirmed malicious npm package (MAL-2025-48296) that executes malicious code on install (malicious version 25.9.29). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-icons-loader (npm)

MAL-2025-48296

Immediate action

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

npm uninstall react-icons-loader

What this malware does

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

1 flagged

25.9.29

Indicators of compromise (SHA-256)

832e2d8edc4d9458500162c7c8fcbc08139c2e9647f28e7d17b8b436f6951675

314774de1d4ed1fd47b7772f0a42332b429c69508668e503c4a06eda00483c30

ae712d84fb05f26d87a1221eb01716626ba3a9a3a5d068425a0b30c0c817d3e2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-icons-loader (version 25.9.29). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-icons-loader across your stack and pipelines.
If you installed it — respond
Remove react-icons-loader 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 react-icons-loader 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-loader 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-loader on npm has been identified as a malicious package (version 25.9.29 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-69v9-mcpc-9hgmRLMA-2025-05497RLUA-2025-05926

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database