Skip to main content
CriticalSecretsOWASP A07:2021CWE-798

How to fix: RubyGems API key in source

RubyGems API keys (rubygems_* / older 32-hex) allow publishing gems as the user, enabling supply-chain takeover.

Why it matters

An exposed RubyGems API key allows an attacker to publish a new malicious version of any gem you own, injecting backdoors into every Ruby application that runs bundle update or gem update, a direct supply-chain attack with wide blast radius.

RubyGems API keys (rubygems_* / older 32-hex) allow publishing gems as the user, enabling supply-chain takeover.

How to fix it

  1. 1Revoke the key at rubygems.org → Edit Profile → API Keys
  2. 2Enable MFA on your RubyGems account to prevent future unauthorized access
  3. 3Audit recent gem publishes for unauthorized versions

Code examples

GitHub Actions: use Trusted Publishing (OIDC)

YAML
# Use RubyGems Trusted Publishing instead of API keys
jobs:
  publish:
    permissions:
      id-token: write
    steps:
      - uses: actions/checkout@v4
      - uses: rubygems/release-gem@v1
        # No RUBYGEMS_API_KEY secret needed with Trusted Publishing

References

Detected automatically by VulnRadar. The check id is secret-rubygems-api-key, stable across every scan so you can filter or diff on it.

See every secrets check

Questions

How severe is RubyGems API key in source?
VulnRadar rates this critical severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id secret-rubygems-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does RubyGems API key in source map to?
It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for rubygems api key in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: RubyGems API key in source | VulnRadar