Which versions of @tunstock/remact-dom are malicious?

The following npm versions of @tunstock/remact-dom are flagged malicious: 19.2.0. Treat any of these as compromised.

How do I remediate @tunstock/remact-dom if I installed it?

@tunstock/remact-dom 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 @tunstock/remact-dom — how do I know if it already compromised me?

If @tunstock/remact-dom 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 @tunstock/remact-dom part of a known attack campaign?

Yes — @tunstock/remact-dom is associated with the IN-MAL-2026-021337 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 @tunstock/remact-dom across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @tunstock/remact-dom (version 19.2.0).

Malicious package

@tunstock/remact-domnpm

Advisory published Oct 9, 2026Updated Oct 9, 2026

@tunstock/remact-dom is a confirmed malicious npm package (MAL-2026-17745) that steals credentials and exfiltrates sensitive data (malicious version 19.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tunstock/remact-dom (npm)

MAL-2026-17745

Immediate action

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

npm uninstall @tunstock/remact-dom

What this malware does

Package @tunstock/remact-dom is a typosquat of react-dom and ships a postinstall script (scripts/setup.js) that runs automatically on npm install. The script collects os.hostname(), os.platform(), os.arch(), Node version, public IP, current working directory, and the consuming project's package.json name and version, then POSTs the payload to the hardcoded lookalike host tele.metry.orgin.net at /api/v1/events via https.request. The exfiltrated payload hardcodes package: 'react-dom', version: '19.2.0', misrepresenting the shipped artifact's identity to the collection endpoint. Author/repo metadata uses lookalike names (m00r0ncr33w, github.com/m00r0ncr33w/act.git, morroncr0w.io). The destination host is not affiliated with any legitimate react-dom infrastructure. The combination of a top-100 package name impersonation, falsified identity in the beacon payload, and automatic install-time exfiltration of installer identifiers to a non-first-party lookalike domain is a victim-tagging reconnaissance beacon staging further supply-chain compromise.

Malicious versions

1 flagged

19.2.0

Indicators of compromise (SHA-256)

32b1034bbfcc4ab6831b76348d4e6c18e427f283ae1cf1661d31f282a3416da8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @tunstock/remact-dom (version 19.2.0).
If you installed it — respond
@tunstock/remact-dom 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 @tunstock/remact-dom 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. @tunstock/remact-dom on npm has been identified as a malicious package (version 19.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021337

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tunstock/remact-dom-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