Which versions of react-dom-helpers are malicious?

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

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

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

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

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

Malicious package

react-dom-helpersnpm

react-dom-helpers is a confirmed malicious npm package (MAL-2026-14253) that steals credentials and exfiltrates sensitive data (malicious version 3.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-dom-helpers (npm)

MAL-2026-14253

Immediate action

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

npm uninstall react-dom-helpers

What this malware does

Package name typosquats react-dom. On require('react-dom-helpers/client'), client.js decodes a base64-obfuscated Slack bot token and channel ID, enumerates local IPv4 addresses via os.networkInterfaces(), fetches the installer's public IP from api.ipify.org, and POSTs the collected host identifiers to https://slack.com/api/chat.postMessage using the hardcoded bearer token. The exfiltration routine is invoked unconditionally at module load. The base64 wrapping of the Slack credential is used to bypass secret scanners.

Malicious versions

1 flagged

3.3.3

Indicators of compromise (SHA-256)

2fae606be0dbd7c79552511c2553ec9e1d081df1279f0bc85502a6c08c0f17fb

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

Campaign

IN-MAL-2026-018368

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database