Are your AWS keys exposed?

Leaked AWS access keys can lead to surprise cloud bills and data theft. Paste a snippet below for an instant in-browser check, or scan a repo or .env and GhostCred flags exposed AKIA keys, secret keys, session tokens, and risky IAM patterns in about a minute.

Check a snippet now

This check runs in your browser, nothing is uploaded. Paste a config file or code snippet and matches appear below as you type.

Patterns checked on this page (3)

AWS access key ID
AWS secret access key
Hardcoded secret assignment (password, token, api_key, secret...)

Scan for exposed AWS keysFree first repo scan, no signup.

What the full scan checks

✓Hardcoded AWS access key IDs (AKIA…) and secret access keys
✓Long-lived keys committed to config or .env files
✓Over-permissive IAM policies and wildcard actions
✓Session tokens and temporary credentials left in config

Why it matters

A single exposed key can let an attacker spin up resources, read your S3 buckets, or rack up massive charges before you notice. Rotating after a breach is far more expensive than catching it first.

Free first scan. No signup. Results in ~60 seconds.

Scan for exposed AWS keys