MAL-2026-17745 Malicious code in @tunstock/remact-dom (npm)
Malicious package
Published
MAL-2026-17745 is a malicious package: @tunstock/remact-dom (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17745/ (Markdown: https://insights.sbomify.com/MAL-2026-17745/index.md)
- Package
- @tunstock/remact-dom
- Registry
- npm
What is MAL-2026-17745?
MAL-2026-17745 is a malicious package in @tunstock/remact-dom, published on 9 Oct 2026.
Official description
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.
What should I do about MAL-2026-17745?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.