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

react-dom-19npm

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

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

What this malware does

The package react-dom-19 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'react-dom-19' @ 3.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
3.0.04.0.0

Indicators of compromise (SHA-256)

11ab4b7b3dba085f3a7108769ba40ce4b223c568b269fd47fa18168d26b42473
45305ef10de1c51596492ab0b2aed61bdba99238b8da096df42d95107dbc1cf0
1e6b5a54efd0bd62412ae002a01495b83a035014f59692e4e942aeaf9fd70d0d

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-dom-19 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-dom-19 across your stack and pipelines.

  2. If you installed it — respond

    Remove react-dom-19 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-dom-19 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-dom-19 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-dom-19 on npm has been identified as a malicious package (versions 3.0.0, 4.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

react-dom-19 (npm) malicious package — MAL-2026-2685 | O3 Security