API Key Leak Intercept
Coverage

Exactly what it covers.

Every site the extension runs on and every pattern it matches, read out of the shipped source by a script. If a claim on this site says the extension catches something, the line that catches it is on this page.

Generated from extension v1.3.4. 52 hostnames, 64 detection patterns, 29 checksum validators.

Where it runs

These are the hostnames declared in the extension manifest. The content script runs on each one before a message is sent, and clean messages are never touched. Universal mode, a Pro and team feature, extends the same scan to every website in the browser.

What it catches on the free plan

Free covers every API key and token pattern below, with no monthly cap. Detection runs locally in the browser. Catch history is not sent on the free plan.

PatternSeverity
OpenAI API keyHigh
Anthropic API keyHigh
AWS Access Key IDHigh
AWS Secret Access KeyHigh
GitHub tokenHigh
Stripe secret keyHigh
Stripe restricted keyHigh
Google API keyHigh
Slack tokenHigh
Slack webhook URLHigh
Discord webhook URLHigh
Telegram bot tokenHigh
Hugging Face tokenHigh
Groq API keyHigh
npm tokenHigh
GitLab tokenHigh
SendGrid API keyHigh
Twilio API keyHigh
JWTHigh
Private key (PEM)High
Bearer tokenHigh
Database connection stringHigh
.env file blockHigh
Password assignmentMedium
Generic secret assignmentMedium

What Pro adds

Personal data, network addresses and custom patterns. The same local detection: the secret values themselves never leave the browser. Severity is the level the warning modal shows.

Personal dataSeverity
Email addressMedium
US SSNHigh
Credit card numberHigh
US phone numberMedium
EU phone numberMedium
IBANHigh
Italian codice fiscaleMedium
Italian partita IVAMedium
Indian Aadhaar numberHigh
Chinese resident IDHigh
Brazilian CPFHigh
Canadian SIN / Australian TFNHigh
NZ IRD numberHigh
German tax ID (Steuer-ID)High
German VAT IDMedium
French NIR (social security)High
Spanish NIF/NIEHigh
Argentine CUILHigh
Chilean RUTHigh
South African ID numberHigh
Russian SNILSHigh
Turkish ID numberHigh
South Korean resident numberHigh
Japanese My NumberHigh
Dutch BSNHigh
Polish PESELHigh
Swedish personnummerHigh
Danish CPR numberHigh
Norwegian fødselsnummerHigh
Finnish hetuHigh
Irish PPS numberHigh
Portuguese NIFHigh
UK National Insurance numberHigh
Indian PAN cardMedium
Mexican CURPHigh
Mexican RFCHigh
Singapore NRIC / FINHigh
Indonesian NIKHigh
NetworkSeverity
IPv4 addressLow

Checksums, not just shapes

Matching a number is easy. These formats are validated against their own check digits and national checksums before the warning fires, which is what keeps a random twelve digits from counting as an Aadhaar:

payment cards (Luhn), Verhoeff check digits, Brazilian CPF, Chinese resident ID, Australian TFN, German Steuer-ID, German VAT ID, French NIR, Spanish NIF/NIE, Argentine CUIL, Chilean RUT, Russian SNILS, Turkish ID number, South Korean resident number, Japanese My Number, Dutch BSN, Polish PESEL, Danish CPR number, Norwegian fodselsnummer, Swedish personnummer, Finnish hetu, Irish PPS number, Portuguese NIF, Italian codice fiscale, Mexican CURP, Mexican RFC, Singapore NRIC/FIN, NZ IRD number, Indonesian NIK.

Your own patterns

Pro and team installs can add regular expressions for internal token formats, and IT can push them to every machine through Chrome policy. The patterns ship inside the extension: no remote configuration can change what counts as a finding.

How to check this page

The tables above are generated from detect.js and manifest.json in the extension source, which is public and MIT. Regenerate this page with:

python3 scripts/gen_coverage.py --extension "/path/to/api-key-leak-intercept/extension"

Source: github.com/dario-cositore/api-key-leak-intercept

Back to API Key Leak Intercept · Install · Privacy policy

Stay in the loop.

Technical breakdowns, new system builds, and lessons from deploying autonomous AI. One email a week, direct to your inbox.

Weekly architectural updates. Unsubscribe anytime.