Which versions of react-dom-v17 are malicious?

The following npm versions of react-dom-v17 are flagged malicious: 15.0.1. Treat any of these as compromised.

How do I remediate react-dom-v17 if I installed it?

react-dom-v17 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed react-dom-v17 — how do I know if it already compromised me?

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

Yes — react-dom-v17 is associated with the IN-MAL-2026-009760 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-dom-v17 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-dom-v17 (version 15.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-dom-v17 across your stack and pipelines.

Malicious package

react-dom-v17npm

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

MAL-2026-10207

Immediate action

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

npm uninstall react-dom-v17

What this malware does

Package name impersonates the widely-used react-dom package (react-dom-v17). package.json declares preinstall: node index.js, which fires automatically on npm install. The preinstall script (index.js) shells out via child_process.exec to run whoami and id, and collects host/user identifiers via os.hostname(), os.userInfo() (username, uid, gid, shell), process.platform, arch, home directory, and cwd. The collected JSON payload is POSTed to a hardcoded Burp Collaborator (oastify.com) subdomain at https://cjzlyigayl8lknm1sjrppofio9u0is6h.oastify.com/detox56. The oastify.com host is an attacker-controlled out-of-band callback endpoint used for reconnaissance beacons and confirms exfiltration intent. The preinstall shell execution surface also establishes arbitrary command execution on the installer at install time, enabling follow-on payloads.

Malicious versions

1 flagged

15.0.1

Indicators of compromise (SHA-256)

f55f6e35ab09a2fcd6521dac51aa4baa4cfa726958bc266a0d56fc14de240a29

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-dom-v17 (version 15.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-dom-v17 across your stack and pipelines.
If you installed it — respond
react-dom-v17 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-dom-v17 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-dom-v17 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-v17 on npm has been identified as a malicious package (version 15.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009760

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-dom-v17-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring