Open
Conversation
Implement real-time detection of secrets in HTTP traffic with optional blocking and masking.
Member
|
Thanks! Can you move this into examples/contrib please? |
Implement real-time detection of sensitive information in HTTP traffic with optional blocking and masking.
Author
|
Done, I've moved it to examples/contrib. Please let me know if anything else is needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement real-time detection of secrets in HTTP traffic with optional blocking and masking.
Description
Adds a new SecretLeakDetector mitmproxy addon that scans live HTTP traffic for leaked credentials in real time. The addon inspects request/response headers, query parameters, and bodies, and supports optional masking and blocking of detected secrets.
Detection coverage:
Anthropic and OpenAI API keys (modern sk-ant-api03- / sk-proj- formats and legacy sk-)
AWS Access Key IDs and Secret Access Keys (with word-boundary guards to avoid base64 false positives)
JWT tokens, Bearer tokens, Google API keys
GitHub PATs (classic ghp_ and fine-grained github_pat_)
Checklist