wallet-crypto-utilsRubyGems
Advisory published Updated
wallet-crypto-utils is a confirmed malicious RubyGems package (MAL-2026-17615) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in wallet-crypto-utils (RubyGems)
What this malware does
RubyGems runs this gem's native extension script ext/req_throttle_mini/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, forks twice into a detached process, waits 20 to 40 minutes and opens a reverse shell that connects /bin/sh to 45.138.12.177 on TCP port 8089. The shell reconnects every 30 seconds. 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 declares a native extension (ext/req_throttle_mini/extconf.rb) that ships no C/C++/Rust sources; the extconf.rb only calls create_makefile('wallet_crypto_utils_native') after a hostile preamble. That preamble decodes a base64 blob and passes the result to eval inside a double-forked detached child. The decoded payload opens a TCP socket to the hardcoded bare IP 45.138.12.177 on port 8089, spawns /bin/sh via IO.popen, and bridges the shell's stdio over the socket with IO.copy_stream in a reconnect loop, yielding an interactive remote shell on the installer's host. Execution is gated behind sandbox/analysis-evasion checks: it skips CI environments, ephemeral/sandbox hostnames, generated analyst usernames, analysis path prefixes, and hosts with short uptime, and only fires when developer artifacts are present on disk (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.bundle, ~/.npmrc). The library file lib/wallet_crypto_utils.rb contains ~707 bytes of base58 helpers that do not require any native code, confirming the extension exists solely to auto-execute the install-time payload. The name suggests a cryptocurrency-wallet utility and the targeted artifact list (SSH keys, git config, gem/bundler/npm credentials) indicates developer-workstation compromise and credential theft follow-on.
The OpenSSF Package Analysis project identified 'wallet-crypto-utils' @ 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 wallet-crypto-utils (2 malicious versions).
If you installed it — respond
wallet-crypto-utils 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 wallet-crypto-utils 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 wallet-crypto-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.