By Null Ventures MCP platform
Menu

supply chain event / NVI-00011134 / Revision 1

Malicious code in aria-live-region-helper (npm)

GitHub lists this malware advisory for aria-live-region-helper. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-2rx7-6p88-g7x4

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.

aria-live-region-helper

source listed
  • = 1.0.0

## Source: amazon-inspector (391a9a163273e36e3945f918ea720b8e10aa462b0aa603d4012b28c557c58570) The package is advertised as an ARIA accessibility helper but ships thunderboltRegistry.js, which executes a top-level IIFE on module load. The IIFE runs shell reconnaissance commands via child_process.execSync (whoami, id, pwd, ifconfig/ip addr, cat /etc/hosts, hostname) and sends their output, together with a beacon containing Node version, process.platform, and PID, via HTTP GET requests to the hardcoded endpoint http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. The package also exports factories under names matching internal Wix thunderbolt registry entry points (thunderboltRegistry, siteAssetsRegistry, editorRegistry, corvidRegistry, etc.) and includes a registry-manifest.min.json mapping those names to parastorage.com unpkg URLs, so that a build pipeline resolving any of those registry names to this package triggers the recon-exfiltration side effect on import. Neither the reconnaissance behavior nor the dxpoc.gt.tc destination is related to the package's advertised accessibility purpose. --- Credit: OpenSSF ([source](h

GitHub Advisory Database

03 / Response

What to do next

  1. 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.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-2rx7-6p88-g7x4 ↗

    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.

  1. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗