Leaked Mistral 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 Mistral step below comes from Mistral's own docs, checked 15 Nov 2026.
Free. No sign-up.
What to do now, for Mistral
Revoke the key now
Delete the key on the API keys page (admins see every key in the organisation), then create a new one. Do this first: until it's revoked, anyone who copied it can keep spending. GitHub alerts the repo's owner about Mistral keys but doesn't report them to Mistral, so nothing disables the key for you.
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.
Check usage for charges that weren't yours
The usage page breaks spend down by model and workspace, not by key. The key list shows when each key was last used. Note the time the key leaked and the time you revoked it.
Cap what any key can spend
Set a usage limit for the organisation in billing, or for each workspace in its settings; access is suspended once it's reached. Pay-as-you-go runs on prepaid credits and stops at zero unless auto-recharge is on.
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.
If someone ran up charges, ask for them back
Contact support through Mistral's help centre. Refunds are reviewed case by case. Say when the key leaked, when you revoked it and which usage wasn't yours.
Checked in Mistral's own docs. Sources: API keys, usage limits, billing. 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 Mistral disable a leaked key for you?
GitHub alerts the repo's owner about Mistral keys but doesn't report them to Mistral, so nothing disables the key for you. Revoke it yourself either way.
Can I cap what a Mistral key spends?
Set a usage limit for the organisation in billing, or for each workspace in its settings; access is suspended once it's reached. Pay-as-you-go runs on prepaid credits and stops at zero unless auto-recharge is on.
How do I see what a leaked Mistral key was used for?
The usage page breaks spend down by model and workspace, not by key. The key list shows when each key was last used.
Will Mistral refund charges from a leaked key?
Contact support through Mistral's help centre. Refunds are reviewed case by case.
How do I find where my Mistral 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
- Leaked OpenAI key
- Leaked Anthropic key
- Leaked Google Gemini key
- Leaked xAI key
- Leaked DeepSeek key
- Leaked OpenRouter key
- Leaked ElevenLabs key
- Leaked Replicate key
- Leaked fal key
- Leaked Groq key
- Leaked Together AI key
- Leaked Hugging Face key
- Leaked Perplexity key
- Leaked Cohere key
- Which providers stop a leaked key for you
- Security checklist for vibe-coded apps