MAL-2026-17791 Malicious code in multichain-rpc (RubyGems)
Malicious package
Published
MAL-2026-17791 is a malicious package: multichain-rpc (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-17791/ (Markdown: https://insights.sbomify.com/MAL-2026-17791/index.md)
- Package
- multichain-rpc
- Registry
- RubyGems
What is MAL-2026-17791?
MAL-2026-17791 is a malicious package in multichain-rpc, published on 11 Oct 2026.
Official description
The gem's extconf.rb, executed automatically by
gem install as a native-extension build step, base64-decodes a Ruby payload and runs it via eval inside a double-forked, stdio-detached background process. The payload opens a TCP socket to the hardcoded host 45.138.12.177 on port 8089 and bridges it to /bin/sh, giving the remote operator an interactive shell on the installer's machine. Execution is gated by developer-host heuristics (presence of ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle, uptime > 1800s) and explicit anti-analysis checks that skip CI, ephemeral, generated-user, and sandbox environments, with a 20-40 minute delay before firing. The rest of the gem is cover: lib/multichain_rpc.rb exports only stub methods (build_id returning 'ok', healthy? returning true), the README advertises an unrelated name (bitcoin-rpc-lite), and extconf.rb declares a native extension (create_makefile('bitcoin_rpc_lite_native')) but ships no C sources, so the file's sole purpose is to run the embedded payload. Installing the gem on a developer workstation yields a full-host remote shell to the attacker.What should I do about MAL-2026-17791?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.