MAL-2026-20103: Malicious code in vuln-app (RubyGems)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (d905ef222b582842835ecb00de0605874b2ccc75e21669725c81de9694aed9bf) The gem declares ext/mkrfconf.rb as a native extension, which RubyGems auto-executes during gem install. The script contains no build logic; instead it collects installer-side data (hostname, login user, cwd, home directory, and the contents of /etc/passwd, /etc/hosts, /etc/resolv.conf), serializes it as JSON, opens a TLS connection to the hardcoded Burp Collaborator subdomain g1im618xdjpuonmkxq16mr33quwlm9cx1.oastify.com:443, and POSTs the payload. A sentinel file.installed is then written. The extension-script naming is used solely to trigger auto-execution on install; no Rakefile is generated and no compilation occurs.
Affected Software
Event History
Frequently Asked Questions
What action triggers the malicious code?
Installing the gem triggers it. RubyGems automatically executes the declared ext/mkrf_conf.rb native-extension script during gem install.
What systems are exposed?
Systems where the listed vuln-app RubyGems package version 1.2.1 is installed are exposed during installation. The script runs in the installer's environment and collects local system and user information.
What data may have been sent if the script ran?
The script collects the hostname, login user, current working directory, home directory, and contents of /etc/passwd, /etc/hosts, and /etc/resolv.conf. It serializes this information as JSON and sends it over TLS.
How can I investigate whether an installation executed the script?
Look for a file named .installed, which the script writes after attempting its network activity. Network telemetry may also show TLS connections to g1im618xdjpuonmkxq16mr33quwlm9cx1.oastify.com on port 443.