MAL-2026-17782 Malicious code in crypto-tax-export (RubyGems)
Malicious package
Published
MAL-2026-17782 is a malicious package: crypto-tax-export (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-17782/ (Markdown: https://insights.sbomify.com/MAL-2026-17782/index.md)
- Package
- crypto-tax-export
- Registry
- RubyGems
What is MAL-2026-17782?
MAL-2026-17782 is a malicious package in crypto-tax-export, published on 11 Oct 2026.
Official description
The gem's native-extension build script ext/crypto_tax_export/extconf.rb runs during
gem install. Before executing its payload it performs sandbox/analysis-evasion checks (CI environment variables, ephemeral/generated hostnames and usernames, known analysis paths, system uptime under 30 minutes, and presence of developer-signal files such as ~/.ssh, ~/.gem/credentials, and ~/.gitconfig). When those checks indicate a real developer workstation, it double-forks a detached, stdio-closed daemon that sleeps a randomized 20-40 minutes and then executes eval(Base64.decode64(...)) on an embedded payload that opens a /bin/sh reverse shell via TCPSocket to the hardcoded bare IP 45.138.12.177:8089 in a reconnect loop. The create_makefile call is a stub targeting an unrelated name (bitcoin_rpc_lite_native), the shipped lib/crypto_tax_export.rb contains only trivial VERSION/build_id/healthy? methods with no tax-export functionality, and the README is for a different package (bitcoin-rpc-lite), indicating the extension script is the gem's sole purpose and the advertised identity is cover.What should I do about MAL-2026-17782?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.