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

gmo-payment-carrierRubyGems

Advisory published Updated

gmo-payment-carrier is a confirmed malicious RubyGems package (MAL-2026-20212) 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-carrier (RubyGems)

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

What this malware does

The gem executes credential-theft code on two surfaces. At install time, extconf.rb (invoked during gem install) collects host identity (hostname, whoami, uname -a, pwd, local IPv4), performs an IMDSv2 token request against 169.254.169.254 and reads the IAM role plus security-credentials, enumerates ECS task metadata, and sweeps environment variables matching DATABASE/DB_/MYSQL/AURORA/POSTGRES/REDIS/RDS, then HTTP GETs the collected data to a hardcoded collector at https://webhook.site/4b2354a7-67fd-4641-92ac-e18bac8c09e8. The library entry point lib/gmo-payment-carrier.rb unconditionally require_relative 'runtime_payload', which repeats the same IMDSv2 credential harvest, ECS metadata read, DB env-var sweep, and host-recon exfil to the same webhook.site URL on every require 'gmo-payment-carrier'. Both paths target the installer / CI / production host and ship AWS IAM role credentials and database secrets to a third-party collector unrelated to any declared publisher.

Malicious versions

1 flagged
0.0.99

Indicators of compromise (SHA-256)

98f131dbde032aa5e99feeaa4175c1fbccf2f634cad07c43ee2b4a0a86044d1b

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    gmo-payment-carrier 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-carrier 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-carrier 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-022888

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gmo-payment-carrier-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-carrier (RubyGems) malicious package — MAL-2026-20212 | O3 Security