Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

react-shieldnpm

react-shield is a confirmed malicious npm package (MAL-2026-14007) that executes malicious code on install (malicious versions 1.10.2, 1.10.3, 1.10.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-shield (npm)

MAL-2026-14007
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-shield

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

3 flagged
1.10.21.10.31.10.4

Indicators of compromise (SHA-256)

168d48206ed936b10520351701ff64b38511462bd75eb9c8724f7039dbc211e9
407d23edc671619cbd75b7d6ba9aa57d1d7a591669dac19d1c2413a78e586362
54d8653ae9a4aa1cec59acb317182ba7375397f9e314c57fb2c89cecd5022459
0a86d21f140bce3d06979252f2591f7234f6147bd04de5cf9dbd61e8dc9008ea

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-shield (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-shield across your stack and pipelines.

  2. If you installed it — respond

    Remove react-shield 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.

  3. Did it already run?

    If react-shield 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.

  4. How O3 protects you

    O3 blocks react-shield 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-shield on npm has been identified as a malicious package (versions 1.10.2, 1.10.3, 1.10.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gmx3-395m-pwc2IN-MAL-2026-017812IN-MAL-2026-017813IN-MAL-2026-017811

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

react-shield (npm) malicious package — MAL-2026-14007 | O3 Security