dex-router-abisRubyGems
Advisory published Updated
dex-router-abis is a confirmed malicious RubyGems package (MAL-2026-17784) 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 dex-router-abis (RubyGems)
What this malware does
The gem's extconf.rb (executed automatically during gem install) decodes a base64-encoded Ruby payload and executes it via a double-forked, detached process that sleeps 20-40 minutes before opening a TCP reverse shell from /bin/sh to the hardcoded remote host 45.138.12.177:8089. Execution is gated by environment checks that look for CI/sandbox/analysis indicators and probe for developer-secret artifacts (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.npmrc, ~/.bundle) so the payload fires only on real developer workstations with credentials present. The create_makefile stub in extconf.rb is a cover: no matching native source exists in the gem tree, and README/metadata identify the package as 'bitcoin-rpc-lite' (makefile target bitcoin_rpc_lite_native) while the published gem name is dex-router-abis, indicating a reused dropper template. Installing this gem grants the operator at 45.138.12.177:8089 interactive shell access to the installer's host with access to local SSH keys, RubyGems publishing credentials, and other developer secrets.
The OpenSSF Package Analysis project identified 'dex-router-abis' @ 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 dex-router-abis (version 0.9.1).
If you installed it — respond
dex-router-abis 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 dex-router-abis 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 dex-router-abis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.