gas-refuel-bridgeRubyGems
Advisory published Updated
gas-refuel-bridge is a confirmed malicious RubyGems package (MAL-2026-17788) that steals credentials and exfiltrates sensitive data (malicious version 0.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in gas-refuel-bridge (RubyGems)
What this malware does
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 payload; the trailing require 'mkmf'; create_makefile is cosmetic.
The OpenSSF Package Analysis project identified 'gas-refuel-bridge' @ 0.9.1 (rubygems) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for gas-refuel-bridge (version 0.9.1).
If you installed it — respond
gas-refuel-bridge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If gas-refuel-bridge was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks gas-refuel-bridge-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.