supply chain event / NVI-00010819 / Revision 1
Malicious code in focus-visible-polyfill-lite (npm)
GitHub lists this malware advisory for focus-visible-polyfill-lite. 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.
focus-visible-polyfill-lite
source listed= 1.0.0
## Source: amazon-inspector (5225b5a8636a589f9b90272ad04c3f4104670a23d5c24b45f6aeaa757a4f2a2b) The package is advertised as a focus-visible polyfill but ships thunderboltRegistry.js, which impersonates Wix thunderbolt internal registry modules (thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, editorRegistry, corvidRegistry, and others) via a Proxy-backed export stub. When the module is required, an IIFE at the top of the file uses child_process.execSync to run host reconnaissance commands (id, whoami, uname -a, ifconfig/ip addr, cat /etc/hosts) and sends the command output along with a beacon (Node version, platform, pid) via plain-HTTP GET requests to a hardcoded attacker-controlled endpoint at http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. The package self-labels the beacon as 'rce-poc'. The shape is a dependency-confusion / typosquat payload: a benign-sounding public package shadows Wix-internal registry names so that a build pipeline resolving these names from the public registry executes the reconnaissance payload with the installer's privileges on module load. --- Credit: OpenSSF ([source](
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-5h59-r5m3-rf9w ↗
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.