supply chain event / NVI-00010050 / Revision 1
Malicious code in gas-refuel-bridge (RubyGems)
GitHub lists this malware advisory for gas-refuel-bridge. 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.
gas-refuel-bridge
source listed= 0.9.1
## Source: amazon-inspector (37bd99ebd0f028669dafee3405a3ac4ebb9e264b7d9bfce963e68b259dfe88a3) The gem's native extension build script extconf.rb base64-decodes an embedded Ruby payload and eval's it during `gem install`. The payload double-forks a detached background process that sleeps for 20-40 minutes and then opens a TCP socket to 45.138.12.177:8089, piping it to /bin/sh in a reconnect loop — a persistent reverse shell on the installer's host. Execution is gated by anti-analysis checks: it skips when common CI environment variables are present, when the hostname looks ephemeral or the username looks auto-generated, when the working directory is under /tmp, /opt/rubygems, or /workspace, when system uptime is under 1800 seconds, and only proceeds when developer-identity markers are present on disk (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle). The gem's advertised identity is a cover story: the gemspec summary describes 'gas refuel bridge helpers', the README is titled 'bitcoin-rpc-lite', and lib/gas_refuel_bridge.rb contains only inert stubs (VERSION, build_id returning 'ok', healthy? returning true). The extension hook is the package's entire functional paylo
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-vpf2-wcf3-pq8j ↗
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.