Which versions of react-hook-form are malicious?

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

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

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

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

Yes — react-hook-form is associated with the GHSA-w8j3-qvc3-h56f 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-form 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-hook-form (version 7.73.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-hook-form across your stack and pipelines.

Malicious package

react-hook-formnpm

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

MAL-2026-2853

Immediate action

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

npm uninstall react-hook-form

What this malware does

The package react-hook-form 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.

Malicious versions

1 flagged

7.73.0

Indicators of compromise (SHA-256)

5aa9ba7a4ea0b89453bdd073b8ffb80b6e3baab6684d5652a1e898c2bacb5a66

17ae372e5061ef357237d48a7812ca65bbc3a49b8a57153df5812d17e9d8eeaa

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-hook-form (version 7.73.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-hook-form across your stack and pipelines.
If you installed it — respond
Remove react-hook-form 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-form 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-hook-form 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-hook-form on npm has been identified as a malicious package (version 7.73.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w8j3-qvc3-h56f

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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