supply chain event / NVI-00009942 / Revision 1
Malicious code in xrp-ledger-utils (RubyGems)
GitHub lists this malware advisory for xrp-ledger-utils. 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.
xrp-ledger-utils
source listed= 0.9.1
## Source: amazon-inspector (1d8cf595b60954811e6adfd0c4a241c696d326b42baf1ed2e7b163e720db44c4) The gem's native extension builder ext/extconf.rb decodes a base64-embedded Ruby payload and eval()s it inside a double-forked, detached child after a randomized 20-40 minute sleep. The payload opens a TCP connection to the hardcoded bare-IP C2 at 45.138.12.177:8089, pipes the socket to /bin/sh, and reconnects in a loop, providing an interactive remote shell on the installer's host. Execution is gated by anti-analysis checks that skip CI runners, sandboxed/ephemeral hosts, synthetic usernames, and fresh VMs, and only fires when developer-workstation indicators are present (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle). The shipped library is an inert stub (build_id='ok', healthy?=true), the README is for an unrelated project ('bitcoin-rpc-lite'), and the Makefile target is bitcoin_rpc_lite_native, so the package has no legitimate advertised functionality; the install-time dropper is its sole purpose. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/mal
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-p4hf-p5fc-85p7 ↗
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.