supply chain event / NVI-00010996 / Revision 1
Malicious code in dom-focus-sentinel (npm)
GitHub lists this malware advisory for dom-focus-sentinel. 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.
dom-focus-sentinel
source listed= 1.0.0
## Source: amazon-inspector (7baf5178b3cd02ae8e6e2c01e8cf305fd9670118428c4d3ef94ac0caef6fc4e8) thunderboltRegistry.js runs an immediately-invoked function at module load that uses child_process.execSync to run host reconnaissance commands (whoami, id, pwd, ifconfig, ip addr, cat /etc/hosts, hostname) and transmits each command's output, along with Node version, platform, and pid, via fetch GET requests to the hardcoded plain-HTTP endpoint http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. The package also structurally impersonates Wix internal registry modules by exporting factories keyed on thunderboltRegistry/siteAssetsRegistry/documentManagementRegistry/editorRegistry/corvidRegistry and shipping a manifest with static.parastorage.com unpkg URLs under dom-focus-sentinel@1.0.0, so the exfiltration IIFE fires whenever a consumer requires any of these registry names. The reconnaissance behavior is unrelated to the declared focus-sentinel purpose, and a `beacon=rce-poc` marker is embedded in the exfil traffic. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ae1ef40954ea15dd560720d58f647c9880a
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-94wj-mm38-wwhp ↗
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.