Why does "Api Keys Exposed" appear in ExposureGrid?

Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.

Could this be a false positive?

Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.

Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

Api Keys Exposed: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

Api Keys Exposed: Secret-like material in public locations increases credential abuse risk if values are valid.

Pattern matches can be false positives - rotate if there is any doubt and remove material from public artifacts.

Search repos/builds, review CI logs, scan dependencies, use vaults for distribution.

Revoke/rotate, purge from history where feasible, add secret scanning in CI, prevent future commits.

Run a scan to verify this fix on your domain

Use the same public scanner as the homepage — results honor your plan tier.

ExposureGrid never displays raw secret values in learning context; findings are redacted aggressively.

Why does "Api Keys Exposed" appear in ExposureGrid?: Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.
Could this be a false positive?: Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.
What should I do after changing configuration?: Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

ExposureGrid continuously monitors these issues and alerts you before they become exploitable.

Run a private scan

Compare plans