Skip to content

Update credential_phishing_suspicious_subject_nlu_financial_urgent.yml #4519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cybher0808 wants to merge 4 commits into
base: main
Choose a base branch
from
+3 −1
Open

Update credential_phishing_suspicious_subject_nlu_financial_urgent.yml #4519

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c5d438e
Update credential_phishing_suspicious_subject_nlu_financial_urgent.yml
cybher0808 May 20, 2026
65f1913
Auto-format MQL and add rule IDs
May 20, 2026
12149b4
Simplify urgency request logic in phishing detection
cybher0808 May 20, 2026
2fbb837
Auto-format MQL and add rule IDs
May 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion detection-rules/credential_phishing_suspicious_subject_nlu_financial_urgent.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,6 +237,7 @@ source: |
"your document settlement",
"your order with amazon",
"your password has been compromised",
"ach? (?:payment|transfer|transaction)",

// cryptocurrency related subjects
'\d{1,2}.\d{1,8}\s(BTC|ETH|SOL|(?:USD[CT])|XRP) Offer Waiting for(\sYour)?\sReview',
Expand All @@ -254,7 +255,7 @@ source: |

// urgency request
and any(ml.nlu_classifier(body.current_thread.text).entities,
.name == "urgency"
.name in ("urgency", "greeting")
)

// org presence
Expand All @@ -264,6 +265,7 @@ source: |
and (
not strings.istarts_with(subject.subject, "re:")
and not any(headers.hops, any(.fields, strings.ilike(.name, "In-Reply-To")))
or not length(headers.reply_to) > 0
)

// the message is unsolicited and no false positives
Expand Down