feat: flag exfil to abused gtld destinations - #17
Merged
Conversation
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
1 participant
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.
All checks pass (873 passed, 11 skipped network e2e, ruff clean, no em dashes). Here is what I changed and why.
What changed
The change is the abused-gTLD allowlist for the data-exfiltration rule. I addressed every gap the completeness critic raised, and fixed a real false positive it surfaced.
Card: 2026-07-24-deepen-rune-1784851194
Built by: bubak4559 Reviewed by: posting.bubak
Opened by GPE on the owner's own repository.