throttle-requestsRubyGems
Advisory published Updated
throttle-requests is a confirmed malicious RubyGems package (MAL-2026-17570) 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 throttle-requests (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 extconf.rb base64-decodes an embedded Ruby payload, writes it to a random path in the temporary directory, and spawns it in the background before running the normal mkmf build. The decoded payload opens a TCP socket to the hardcoded host 45.138.12.177 on port 8090 and bridges that socket to /bin/sh via IO.popen in a persistent loop, granting the remote host interactive shell access on the installer's machine during gem install. The payload destination and shell-exec behavior are hidden inside a base64 literal decoded only at install time, with a bare rescue swallowing errors. The behavior is unrelated to the package's stated purpose (a request throttling library) and runs automatically as part of the gem's native extension build phase.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for throttle-requests (2 malicious versions).
If you installed it — respond
throttle-requests 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 throttle-requests 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 throttle-requests-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.