Create link_url_with_recipient_targeting_and_special_characters.yml #3715
+45
−0
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
github-actions
bot
added
the
in-test-rules
github-actions bot
added a commit
that referenced
this pull request
Dec 24, 2025
…and special 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.
Description
This rule catches phishing links that try to look personalized by embedding the recipient's email (sometimes base64 encoded) in URLs that have sketchy path patterns with special characters like ! or @. We're specifically looking for simple single-path URLs ending in $ or * which is a common pattern we've seen in credential harvesting campaigns. The single recipient check helps reduce noise since these targeted attacks typically go to one person at a time.
Associated hunts
Other hunts can be found in the ticket for customer environment ones.