request-guardRubyGems
Advisory published Updated
request-guard is a confirmed malicious RubyGems package (MAL-2026-17569) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in request-guard (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 8090. 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's native-extension build script ext/req_throttle_mini/extconf.rb base64-decodes a Ruby payload, writes it to a random file under Dir.tmpdir, and spawns it with the Ruby interpreter before calling create_makefile. The decoded payload opens a TCP connection to the hardcoded bare IP 45.138.12.177 on port 8090 and bridges /bin/sh to the socket in a persistent reconnect loop, giving a remote party interactive shell access on the installer's host. No C/C++ source files are shipped in the gem, so the create_makefile('request-guard_native') call is cover: the extension exists solely to execute the hidden payload at install time. Installing this gem auto-executes the extension and triggers the reverse shell on the installing machine.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for request-guard (2 malicious versions).
If you installed it — respond
request-guard 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 request-guard 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
- SafeDep · finder
Detect & block this
O3 blocks request-guard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.