Skip to content

Leaked fal 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 fal step below comes from fal's own docs, checked 15 Nov 2026.

Free. No sign-up.

Whose key leaked?
Where did it leak?

What to do now, for fal

  1. Revoke the key now

    Revoke the key on the keys page (this can't be undone), then create a new one. Do this first: until it's revoked, anyone who copied it can keep spending. GitHub doesn't scan for fal keys, so nobody will warn you about one in a public repo.

    fal 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

    Check usage in your fal dashboard. Note the time the key leaked and the time you revoked it.

    fal dashboard

  4. Cap what any key can spend

    fal is prepaid: requests are rejected once your credit falls below a threshold. There's no separate spend limit setting, so keep the balance small.

  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

    Email support@fal.ai. fal has no stated policy on usage from leaked keys. Say when the key leaked, when you revoked it and which usage wasn't yours.

    support@fal.ai

Checked in fal's own docs. Sources: revoking a key, FAQ. 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 fal disable a leaked key for you?

GitHub doesn't scan for fal keys, so nobody will warn you about one in a public repo. Revoke it yourself either way.

Can I cap what a fal key spends?

fal is prepaid: requests are rejected once your credit falls below a threshold. There's no separate spend limit setting, so keep the balance small.

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

Check usage in your fal dashboard.

Will fal refund charges from a leaked key?

Email support@fal.ai. fal has no stated policy on usage from leaked keys.

How do I find where my fal key leaked?

Search your code, your git history and your live site's JavaScript for the first few characters of the old key. Common places are browser code, a committed .env or local settings file, and screenshots.

Other providers