Skip to content

Leaked Anthropic (Claude) API key? What to do now

Revoke it first, then check what it was used for, cap what your keys can spend and clean up where it leaked. Every Anthropic step below comes from Anthropic's own docs, checked 15 Nov 2026.

Free. No sign-up.

Whose key leaked?
Where did it leak?

What to do now, for Anthropic

  1. Revoke the key now

    On the API keys page, open the ⋯ menu on the key, choose Delete API key, then create a new one. Do this first: until it's revoked, anyone who copied it can keep spending. Anthropic deactivates keys found in public GitHub repos and emails you.

    Claude Console API keys

  2. Keep the new key on the server

    Put the new key only in a server-side secret: your host's environment settings, your builder's secrets, or Supabase function secrets. Never in a variable starting NEXT_PUBLIC_, VITE_ or EXPO_PUBLIC_, which are sent to every visitor.

    Lovable secretsBolt secretsSupabase function secrets

  3. Check usage for charges that weren't yours

    The usage page can filter by API key. Note the time the key leaked and the time you revoked it.

    Claude Console usage

  4. Cap what any key can spend

    Set your own monthly spend limit, below your tier's cap; requests stop once it's reached. It covers the organisation or one workspace, not one key. Usage is paid from prepaid credits, so check whether auto-reload is on.

    Claude Console spend limits

  5. Clean up the repo, after revoking

    Remove the key from the code and the git history, but only once it's revoked: anyone who cloned the repo, or a fork, still has it. Then turn on push protection, so GitHub blocks the next key you try to push.

    GitHub: removing sensitive dataGitHub: push protection

  6. If someone ran up charges, ask for them back

    Contact support from the Claude help centre. Anthropic has no stated policy on usage from leaked keys, and credit purchases aren't refundable. Say when the key leaked, when you revoked it and which usage wasn't yours.

    Claude support

Checked in Anthropic's own docs. Sources: compromised keys, cost and usage reporting, rate limits, API key best practices, getting an API key. Dashboards move, so if a link is out of date, look for the same setting under account or organisation settings.

Then find every other copy, with your coding agent

Find every place an API key or other secret is exposed in this project, and fix it. Search the code, env files, config and local settings files (such as .claude/settings.local.json), the full git history (with gitleaks or a similar scanner) and the built browser bundle. Flag any secret in a variable with a public prefix such as NEXT_PUBLIC_, VITE_ or EXPO_PUBLIC_, and any AI provider called from browser code. Move every AI call into a server route or function that reads its key from a server-only variable, add .env and local settings files to .gitignore, and list each key that was exposed and where, so I can revoke it. Don't rewrite git history.

Questions

Does Anthropic disable a leaked key for you?

Anthropic deactivates keys found in public GitHub repos and emails you. Revoke it yourself either way.

Can I cap what an Anthropic key spends?

Set your own monthly spend limit, below your tier's cap; requests stop once it's reached. It covers the organisation or one workspace, not one key. Usage is paid from prepaid credits, so check whether auto-reload is on.

How do I see what a leaked Anthropic key was used for?

The usage page can filter by API key.

Will Anthropic refund charges from a leaked key?

Contact support from the Claude help centre. Anthropic has no stated policy on usage from leaked keys, and credit purchases aren't refundable.

How do I find where my Anthropic key leaked?

Search your code, your git history and your live site's JavaScript for “sk-ant-” (how Anthropic keys start). Common places are browser code, a committed .env or local settings file, and screenshots.

Other providers