supply chain event / NVI-00011113 / Revision 1
Malicious code in css-txedrf-polyfill (npm)
GitHub lists this malware advisory for css-txedrf-polyfill. 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.
css-txedrf-polyfill
source listed= 1.0.0
## Source: amazon-inspector (7d70c660ff3138360df0239fc6ef3db7beaca61ca069bc2d108ed893c68acb63) thunderboltRegistry.js executes an IIFE at require time that runs OS reconnaissance commands (id, whoami, uname -a, ifconfig/ip addr, cat /etc/hosts) via child_process.execSync, URL-encodes the output together with hostname, node version, platform, and pid, and POSTs/GETs each result via fetch to the hardcoded endpoint http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f over plain HTTP. The package's exported module names (thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, editorRegistry, corvidRegistry) impersonate Wix thunderbolt internal registry modules and the manifest references static.parastorage.com URLs, consistent with a dependency-confusion lure aimed at a private Wix namespace. Any consumer that requires one of these modules triggers the reconnaissance and exfiltration to the attacker-controlled host. --- 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-xjj7-95rf-xxgq ↗
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.