By Null Ventures MCP platform
Menu

supply chain event / NVI-00008706 / Revision 1

Malicious code in @sudobility/indexer_client (npm)

GitHub lists this malware advisory for @sudobility/indexer_client. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-2gvv-vgvw-559c

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.

@sudobility/indexer_client

source listed
  • = 0.0.146

## Source: amazon-inspector (b374713629b9be645f22b21fab5376e57a55d3001c72a1e55e1e8dfb6e40a27b) The package's postinstall hook executes scripts/miner.sh, which uses curl to download a gzipped payload from https://amplify-gursha-dev-121835-deployment.s3.amazonaws.com/ (a presigned S3 URL embedding AWSAccessKeyId ), decompresses it to /tmp/.smi, and runs it. When executed as root or when passwordless sudo is available, it invokes `/tmp/.smi agent` with elevated privileges to perform a persistent agent install (the script's own comments reference stealth renames, cron, and tor/relay components). In the unprivileged branch it extracts an embedded XMRig binary, writes a hardcoded Monero pool configuration to $HOME/.sysmond.json, copies the binary into $HOME/.local/lib/ under a randomized system-component name drawn from a list including edid-mon, smmon, irqstatsd, and kmod-cache, and launches it via nohup in the background. A second attacker-controlled endpoint networkservicesupp.flashhub.net:8443 is referenced for relay/C2. The S3 URL also exposes a third-party AWS access key as an IOC. --- Credit: OpenSSF ([source](https://githu

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-2gvv-vgvw-559c ↗

    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 ↗