supply chain event / NVI-00011132 / Revision 1
Malicious code in css-dwsawd-polyfill (npm)
GitHub lists this malware advisory for css-dwsawd-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-dwsawd-polyfill
source listed= 1.0.0
## Source: amazon-inspector (1c370cda09695e44d06a44bc14d14817edadc047e4dad0314edcfc752be796e9) The package name mimics a Wix thunderbolt polyfill and ships a registry-manifest.min.json that aliases legitimate @wix thunderbolt registry module names to thunderboltRegistry.js. On require, thunderboltRegistry.js runs an IIFE that uses child_process.execSync to execute shell reconnaissance (id, whoami, uname -a, ifconfig/ip addr, /etc/hosts) and fetches http://dxpoc.gt.tc/callback.php/bb8968d0f67000433bf7005dd5ad2d1f with the command outputs plus hostname, pid, platform, node version, and a site identifier as query parameters, tagged 'rce-poc'. A fallback path constructs a fresh Module instance to re-resolve child_process if the require cache is stubbed, ensuring execution. The destination is plain HTTP to an unrelated external host and is not caller-configurable. --- 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-xvvh-qgjc-g49x ↗
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.