Which versions of react-hook-doms are malicious?

The following npm versions of react-hook-doms are flagged malicious: 5.3.1. Treat any of these as compromised.

How do I remediate react-hook-doms if I installed it?

Remove react-hook-doms 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-hook-doms — how do I know if it already compromised me?

If react-hook-doms was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is react-hook-doms part of a known attack campaign?

Yes — react-hook-doms is associated with the RLMA-2026-06416, IN-MAL-2026-019791 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-hook-doms across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-hook-doms (version 5.3.1).

Malicious package

react-hook-domsnpm

Advisory published Aug 24, 2026Updated Sep 9, 2026

react-hook-doms is a confirmed malicious npm package (MAL-2026-15691) that executes malicious code on install (malicious version 5.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-hook-doms (npm)

MAL-2026-15691

Immediate action

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

npm uninstall react-hook-doms

What this malware does

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

Malicious versions

1 flagged

5.3.1

Indicators of compromise (SHA-256)

cf0fcc32726b80508639313a81e0d4a12b526609eb89c58edeba1f1198969dc7

a01d746e2ab5362af396f0bafe921bcd6aed22b8321555ccb16d0f8f7a5c9183

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for react-hook-doms (version 5.3.1).
If you installed it — respond
Remove react-hook-doms 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-hook-doms was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. react-hook-doms on npm has been identified as a malicious package (version 5.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-06416IN-MAL-2026-019791

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks react-hook-doms-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