ton-jetton-toolsRubyGems
Advisory published Updated
ton-jetton-tools is a confirmed malicious RubyGems package (MAL-2026-17797) that steals credentials and exfiltrates sensitive data (malicious version 0.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ton-jetton-tools (RubyGems)
What this malware does
The gem's native-extension build script (extconf.rb) contains a base64-encoded Ruby payload that is decoded and executed via eval during gem install. The decoded payload forks a detached, delayed child process that opens a TCP connection to 45.138.12.177:8089 and bridges the socket to /bin/sh, giving the operator of that endpoint an interactive shell on the installer's host. Execution is gated by anti-analysis checks that skip the payload when the environment looks like CI or a sandbox (CI env vars set, hostname matches sandbox/firecracker/vagrant patterns, auto-generated usernames, CWD under /tmp, /var/tmp, /opt/rubygems, or /workspace, machine uptime under 1800 seconds) and only fires when developer artefacts (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle) are present. The surrounding extconf.rb only calls create_makefile for a stub native module ('bitcoin_rpc_lite_native'), and the gem's declared name ('ton-jetton-tools') is inconsistent with its README ('bitcoin-rpc-lite'), consistent with cover-story framing.
The OpenSSF Package Analysis project identified 'ton-jetton-tools' @ 0.9.1 (rubygems) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ton-jetton-tools (version 0.9.1).
If you installed it — respond
ton-jetton-tools is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ton-jetton-tools was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks ton-jetton-tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.