supply chain event / NVI-00009975 / Revision 1
Malicious code in airdrop-eligibility-check (RubyGems)
GitHub lists this malware advisory for airdrop-eligibility-check. 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.
airdrop-eligibility-check
source listed= 0.9.1
## Source: amazon-inspector (eb3461788cd7b809ba613c07b39b583fb968ce927ccfc15433673e2731ca68d8) The gem's extconf.rb, executed during `gem install`, decodes a base64 Ruby payload and eval's it inside a detached double-forked (Process.setsid) child process after a randomized 20–40 minute sleep. The payload opens a TCPSocket to the hardcoded endpoint 45.138.12.177:8089, spawns /bin/sh via IO.popen, and bridges stdio in both directions, providing an interactive reverse shell on the installer's host. Detonation is gated by anti-analysis checks that skip execution in CI, on ephemeral hostnames, under generated usernames, inside analysis paths, and when /proc/uptime is under 1800 seconds; it only arms when developer-credential files are present (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.bundle, ~/.npmrc). The gem has no real functionality: the gemspec name (airdrop-eligibility-check) does not match the README (bitcoin-rpc-lite) or the created makefile (bitcoin_rpc_lite_native), and the lib entry is a trivial stub returning 'ok'. The native-extension build is used solely as a vehicle for the dropper. --- Credit: OpenSSF ([source](https://g
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-qmg2-cxmc-2xm5 ↗
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.