supply chain event / NVI-00009669 / Revision 1
Malicious code in dex-router-abis (RubyGems)
GitHub lists this malware advisory for dex-router-abis. 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.
dex-router-abis
source listed= 0.9.1
## Source: amazon-inspector (a8f8b62993678b4f720468a05ef91f6fdcc864dd6be78d1ffc6bd14125f18d8f) 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. --- Credit: [OpenSSF](https://github.com/ossf/mali
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-j34r-6fqr-vh5p ↗
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.