Typosquat credential-theft gems: gmo-payment / gmo-payment-carrier exfiltrate AWS IAM and DB secrets
Severity: critical · Patch status: no-fix-needed · Since 2026-11-19
Two malicious RubyGems, gmo-payment and gmo-payment-carrier (both version 0.0.99, typosquats of GMO Payment Gateway's legitimate packages), were published with credential-theft code. At install time, extconf.rb collects host identity (hostname, user, uname, cwd, local IP), queries AWS IMDSv1/IMDSv2 for IAM role security credentials, reads ECS task metadata, and sweeps environment variables matching DATABASE/DB/MYSQL/AURORA/POSTGRES/REDIS/RDS, exfiltrating everything via HTTP to a hardcoded webhook.site collector. The library entry points unconditionally require a runtimepayload stage that repeats the same harvest on every require, hitting installers, CI, and production hosts. No patched versions exist; the gems should be removed. Disclosed 2026-11-19 via GitHub Advisory Database (OpenSSF/amazon-inspector).
What to do
- Immediately remove/uninstall gmo-payment and gmo-payment-carrier 0.0.99 from all Gemfiles, lockfiles, and hosts
- Rotate any AWS IAM role credentials that could have been exposed via IMDS on affected install/CI/production machines
- Rotate database, MySQL/Aurora/Postgres, and Redis credentials found in environment variables on those hosts
- Audit install and CI logs and network egress for connections to webhook.site/4b2354a7-67fd-4641-92ac-e18bac8c09e8
- Block egress to the collector endpoint and to 169.254.169.254 from build environments where feasible; enforce IMDSv2 with hop limit restrictions
- Pin dependencies and verify gem provenance before installing
Sources
All live incidents on Threat Watch