supply chain event / NVI-00009734 / Revision 1
Malicious code in @tunstock/remact-dom (npm)
GitHub lists this malware advisory for @tunstock/remact-dom. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@tunstock/remact-dom
source listed= 19.2.0
## 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. --- Credit: [OpenSSF](https://github.com/ossf/
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-gjvr-3qjw-56fx ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.