By Null Ventures MCP platform
Menu

supply chain event / NVI-00009736 / Revision 1

Malicious code in solaan-ruby (RubyGems)

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

source listedactiveGHSA-vwg4-2hf7-g55g

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.

solaan-ruby

source listed
  • = 1.0.0

## Source: amazon-inspector (e44549858fa90854aa5c3acae5440714ef5271cabb67243d4c82713ca3c108f7) The gem's native-extension build script (extconf.rb) carries a base64-encoded Ruby payload that executes at `gem install` time via the standard mkmf build hook. The accompanying C source is a 2-line empty stub, so building a native extension is not the real purpose of the file — the gem exists to run the embedded payload. The payload XOR-reconstructs a URL pointing at the hardcoded bare-IP endpoint http://45.138.12.177:8092/wgkit.tar.gz, curls the tarball to /tmp/.w1.tgz with no integrity check, extracts it to /tmp/.w1, and runs `bash /tmp/.w1/wg_install.sh`, giving the operator of that IP arbitrary code execution on the installer's host. Execution is gated by evasion checks that abort on CI environments, hostnames matching uvm/firecracker/sandbox/vagrant, usernames matching scanner patterns, working directories under /tmp or /opt/rubygems, and `/proc/uptime` under 1800 seconds, and only proceeds when developer artifacts are present on disk (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.bundle). The dropper additionally forks a detached child and sleeps a randomized 20–40 minutes before th

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-vwg4-2hf7-g55g ↗

    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 ↗