crylto-toolboxRubyGems
Advisory published Updated
crylto-toolbox is a confirmed malicious RubyGems package (MAL-2026-17591) 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 crylto-toolbox (RubyGems)
What this malware does
RubyGems runs this gem's native extension script ext/crylto-toolbox/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's extconf.rb is not a native-extension build script. It contains a base64-encoded Ruby payload that, after gating on anti-analysis checks, downloads and executes an attacker-controlled shell script at install time. The anti-analysis gate inspects CI environment variables, hostname patterns (uvm/firecracker/sandbox/vagrant), username patterns (uA\d+, sandbox/tester/analys/scanner), working-directory prefixes (/tmp, /var/tmp, /opt/rubygems, /workspace), /proc/uptime (>1800s), and the presence of developer artifacts (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle) to restrict execution to real developer machines. When the gate passes, extconf.rb forks a detached process that sleeps 20-40 minutes, then reconstructs a URL by XOR-decoding a hex blob with key 'usv\x9a' resolving to http://45.138.12.177:8092/wgkit.tar.gz, downloads the archive to /tmp/.w1.tgz with no TLS and no integrity check, extracts it, and runs bash /tmp/.w1/wg_install.sh via system(). The package name is a typo of 'crypto-toolbox'. The combination of obfuscated URL reconstruction, bare-IP plaintext HTTP delivery, detached delayed execution, sandbox-evasion gating keyed on developer-only artifacts, and execution of arbitrary attacker-supplied bash during gem install is an install-time dropper on the installer's host.
The OpenSSF Package Analysis project identified 'crylto-toolbox' @ 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 crylto-toolbox (version 1.0.0).
If you installed it — respond
crylto-toolbox 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 crylto-toolbox 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 crylto-toolbox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.