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

wac-react-domnpm

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

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

What this malware does

The package wac-react-dom was found to contain 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.

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

It is considered malicious because:

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

Malicious versions

1 flagged
99.99.1

Indicators of compromise (SHA-256)

841b27b7a49af4c4a8f99dc6493bbc2049f990a76faa482b57e8b3b692ef0a6a
a3574245c1ec6c0d46b337b9600a38046ef129489605e5e108fcaaed753d50c9
483203b2478e5e472201a6f6d8efef0353ca7fb2ccf429996cc59e2574b2e497

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

  2. If you installed it — respond

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

Campaign

GHSA-6w23-3m7m-ffrm

References

Credits

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

Detect & block this

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

wac-react-dom (npm) malicious package — MAL-2026-201 | O3 Security