If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (32b1034bbfcc4ab6831b76348d4e6c18e427f283ae1cf1661d31f282a3416da8)
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.