ethereum-tx-helperRubyGems
Advisory published Updated
ethereum-tx-helper is a confirmed malicious RubyGems package (MAL-2026-17601) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ethereum-tx-helper (RubyGems)
What this malware does
RubyGems runs this gem's native extension script ext/ethereum-tx-helper/extconf.rb during gem install. The script exits without action on CI runners and sandboxes, based on CI environment variables, the hostname, the username and the working directory. It continues if the system uptime is over 30 minutes and the home directory holds .ssh, .gitconfig, .npmrc, .gem/credentials or .bundle. It then decodes a Base64 Ruby payload and forks twice into a detached process. After 20 to 40 minutes the payload downloads http://45.138.12.177:8092/wgkit.tar.gz to /tmp/.w1.tgz with curl, extracts it to /tmp/.w1/, runs wg_install.sh with bash and deletes both. The payload stores the URL XOR-encoded with the key usv\x9a. The Ruby code in lib/ is a decoy. The RubyGems account reqthrottle_3474 published this gem and 41 others with the same loader on 2026-10-05.
The gem advertises Ethereum transaction helpers but ships only an empty C stub (ext/ethereum-tx-helper/ethereum-tx-helper.c: Init_EthereumTxHelper(){}) and a tiny BIP39 word-list helper in lib. All real behavior lives in ext/ethereum-tx-helper/extconf.rb, which runs during gem install as the native-extension build step. extconf.rb executes an eval() of a base64-encoded Ruby payload that first fingerprints the host for analysis/CI/sandbox markers and for developer-machine signals (~/.ssh, ~/.gem/credentials, ~/.gitconfig, ~/.npmrc, ~/.bundle); on a host that looks like a real developer workstation it double-forks a detached background process, sleeps 20-40 minutes to evade sandbox timing, then curls a tarball from a bare-IP endpoint at http://45.138.122.177:8092/wgkit.tar.gz into /tmp/.w1.tgz and executes bash /tmp/.w1/wg_install.sh. The destination URL is not present in cleartext — it is reconstructed at runtime by XOR-decoding a hex blob against the 4-byte key "usv\x9a", specifically to defeat static URL extraction. The package name and homepage (ethereum-tx-helper.dev) impersonate a crypto-developer utility to attract installs by developers whose machines are the exact targets the dropper's gating selects for.
The OpenSSF Package Analysis project identified 'ethereum-tx-helper' @ 1.0.0 (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 ethereum-tx-helper (version 1.0.0).
If you installed it — respond
ethereum-tx-helper 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 ethereum-tx-helper 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
- SafeDep · finder
Detect & block this
O3 blocks ethereum-tx-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.