NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

gmo-paymentRubyGems

Advisory published Updated

gmo-payment is a confirmed malicious RubyGems package (MAL-2026-20211) that steals credentials and exfiltrates sensitive data (malicious version 0.0.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gmo-payment (RubyGems)

MAL-2026-20211
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall gmo-payment

What this malware does

The gem ships a native-extension build script (extconf.rb) that runs automatically during gem install. It collects host identifiers (hostname, whoami, uname output, working directory, local IPv4), queries the AWS Instance Metadata Service (both IMDSv1 and IMDSv2) to retrieve IAM role security credentials, pulls ECS task metadata, harvests environment variables matching DATABASE/DB_/MYSQL/AURORA/POSTGRES/REDIS/RDS, and POSTs the collected data to the hardcoded endpoint https://webhook.site/4b2354a7-67fd-4641-92ac-e18bac8c09e8. The script then writes an empty Makefile to disguise the lack of an actual build. A second stage in lib/gmo/payment.rb unconditionally require_relatives runtime_payload.rb, whose top-level code repeats the same IMDS credential fetch, ECS metadata lookup, and database/cache environment variable harvest on every require of the gem, exfiltrating to the same webhook endpoint. The file is self-labeled as a malicious native extension hook.

Malicious versions

1 flagged
0.0.99

Indicators of compromise (SHA-256)

4536bede455c58b0be6819cbc85b4566d1c567bfedc370aac7f97a3aacc9776b

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for gmo-payment (version 0.0.99).

  2. If you installed it — respond

    gmo-payment 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.

  3. Did it already run?

    If gmo-payment 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

No. gmo-payment on RubyGems has been identified as a malicious package (version 0.0.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022887

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gmo-payment-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

gmo-payment (RubyGems) malicious package — MAL-2026-20211 | O3 Security