supply chain event / NVI-00010031 / Revision 1
Malicious code in seed-phrase-validator (RubyGems)
GitHub lists this malware advisory for seed-phrase-validator. 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.
seed-phrase-validator
source listed= 0.9.1
## Source: amazon-inspector (fb8d12a066c24d672bf16efe57267c46c727592ee21beb0e2accb3bb6e4bfb3a) The gem declares a native extension but ships no C/C++/Rust source. extconf.rb exists solely to execute at `gem install` time. It decodes a base64-encoded Ruby payload and runs it via eval inside a detached fork (Process.setsid, randomized sleep of 1200+rand(1200) seconds) so execution survives the install process. The decoded payload opens a TCP socket to the hardcoded bare IP 45.138.12.177:8089 and bridges it to /bin/sh, giving an interactive remote shell on the installer's host. Execution is gated by anti-analysis checks that skip CI runners, ephemeral/sandbox hosts, generated usernames, analysis paths, and low-uptime machines, firing only when developer artifacts such as ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, or ~/.bundle are present on the host. Package identity is inconsistent: the gem is named seed-phrase-validator, the README is titled bitcoin-rpc-lite, and the makefile target is bitcoin_rpc_lite_native, with no matching native sources in the tree. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/
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-vfwp-3q5f-qqrh ↗
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.