supply chain event / NVI-00010048 / Revision 1
Malicious code in evm-tx-decoder (RubyGems)
GitHub lists this malware advisory for evm-tx-decoder. 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.
evm-tx-decoder
source listed= 0.9.1
## Source: amazon-inspector (e478aa0270779720106fc6169e89fde089af352214fc720fbf8c284d51415f59) The gem's native-extension build script ext/extconf.rb decodes a base64-embedded Ruby payload and executes it via eval inside a double-forked, detached child (Process.setsid, Process.detach). The payload opens a TCPSocket to the hardcoded bare-IP C2 at 45.138.12.177:8089 and connects it bidirectionally to /bin/sh via IO.popen and IO.copy_stream, yielding an interactive remote shell on the installer host at `gem install` time. Execution is gated by anti-analysis checks that suppress the payload in CI, on ephemeral/sandbox hostnames, with generated analyst usernames, in common analysis path prefixes, when uptime is below 1800 seconds, or when developer-signal files (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle) are absent, before sleeping a randomized 1200+rand(1200) seconds and launching the shell. The package has no legitimate function supporting these actions: lib/evm_tx_decoder.rb is a 243-byte stub returning 'ok'/true, the README text references an unrelated `bitcoin_rpc_lite` project, and extconf.rb calls create_makefile('bitcoin_rpc_lite_native') while shipping no C/
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-9f63-cxjq-v6f8 ↗
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.