By Null Ventures MCP platform
Menu

supply chain event / NVI-00009999 / Revision 1

Malicious code in etherdum.rb (RubyGems)

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

source listedactiveGHSA-f6c2-r38w-6v9x

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.

etherdum.rb

source listed
  • = 1.0.0

## Source: amazon-inspector (a27b2952de0064d1745d45f18fc1ab974e48cfe185b8f41e90447265be1a880f) The gem declares ext/etherdum.rb/extconf.rb as a native extension, but the accompanying C source is an empty Init stub and the Ruby library is a trivial word list with no cryptography. extconf.rb, which RubyGems runs automatically on `gem install`, base64-decodes and evals a Ruby payload that XOR-decodes a hardcoded URL (http://45.138.217.89:2/wgkit.tar.gz, overridable via WG_KIT_URL), downloads a tarball to /tmp/.w1.tgz, extracts it, and executes wg_install.sh over plaintext HTTP from a bare IP. Execution is wrapped in a double-forked, detached child with stdio redirected to /dev/null and a 20-40 minute sleep before firing. Anti-analysis gating skips CI environments, ephemeral/sandbox hostnames (uvm, firecracker, sandbox, vagrant, fc-vm), generated-looking usernames (uA\d+, sandbox/tester/analys/scanner), analysis paths (/opt/rubygems, /tmp, /workspace), machines with uptime under 1800 seconds, and systems lacking developer artifacts, requiring the presence of ~/.ssh, ~/.gem/credentials, ~/.bundle,.gitconfig, or.npmrc before executing. The package name typosquats 'ethereum' and the nativ

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-f6c2-r38w-6v9x ↗

    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 ↗