MAL-2026-17801 Malicious code in web3-signer-kit (RubyGems)
Malicious package
Published
MAL-2026-17801 is a malicious package: web3-signer-kit (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-17801/ (Markdown: https://insights.sbomify.com/MAL-2026-17801/index.md)
- Package
- web3-signer-kit
- Registry
- RubyGems
What is MAL-2026-17801?
MAL-2026-17801 is a malicious package in web3-signer-kit, published on 11 Oct 2026.
Official description
The gem's extconf.rb decodes a base64 literal and eval's it at
gem install time inside a double-forked, session-detached child whose stdio is redirected to /dev/null. The decoded payload opens a TCPSocket to 45.138.12.177:8089 and bridges a /bin/sh process over that socket via IO.popen + IO.copy_stream, yielding full-host remote code execution for the operator of that endpoint. Execution is gated by sandbox-evasion checks that skip CI, ephemeral/short-uptime hosts, analyst-style usernames, and analysis paths, and requires developer artifacts (~/.ssh, ~/.gitconfig, ~/.gem/credentials) to be present before firing; a randomized sleep of 1200+rand(1200) seconds further delays detonation. The package has no legitimate functionality: metadata describes it as a 'web3 signer kit' while the README advertises bitcoin-rpc-lite, the library exposes only stub methods (build_id, healthy?), and extconf.rb calls create_makefile('bitcoin_rpc_lite_native') with no C sources shipped. The entire gem is a decoy wrapper around the dropper in extconf.rb.What should I do about MAL-2026-17801?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.