MAL-2026-17779 Malicious code in airdrop-eligibility-check (RubyGems)
Malicious package
Published
MAL-2026-17779 is a malicious package: airdrop-eligibility-check (RubyGems). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17779/ (Markdown: https://insights.sbomify.com/MAL-2026-17779/index.md)
- Package
- airdrop-eligibility-check
- Registry
- RubyGems
What is MAL-2026-17779?
MAL-2026-17779 is a malicious package in airdrop-eligibility-check, published on 11 Oct 2026.
Official description
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.What should I do about MAL-2026-17779?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.