supply chain event / NVI-00010480 / Revision 1
Malicious code in wix-reg-poc-bypass (npm)
GitHub lists this malware advisory for wix-reg-poc-bypass. 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.
wix-reg-poc-bypass
source listed= 1.0.0
## Source: amazon-inspector (4b0b4a2bb63a48ca7c9f712068de893526ec0e3515ffd367f37b5c251034965a) The package shadows internal Wix registry module names (thunderboltRegistry, corvidRegistry, editorRegistry, siteAssetsRegistry, and others) and ships a registry-manifest.min.json pointing at a parastorage CDN URL so that loading one of these registry entries resolves to this package's code. thunderboltRegistry.js runs an IIFE at module load that executes `id` and `hostname` via child_process.execSync, combines the output with process.platform, process.arch, process.pid, and process.version, and sends the values as query-string parameters in a fetch() call to the hardcoded collector https://webhook.site/43022177-de67-4d5c-a6df-33083b2b026f. The exported factories return Proxy stubs rather than implementing the real registry contracts, so the module's only effective behavior when loaded by a Wix SSR host is the reconnaissance beacon. --- 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-v43v-p74g-hrf9 ↗
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.