Detection rules › Sublime MQL
Service abuse: Google Drive share from new reply-to domain
A Google Drive sharing notification containing a reply-to address from a recently registered domain (less than 30 days old). The reply-to domain does not match any organizational domains.
Threat classification
Sublime's own taxonomy (not MITRE ATT&CK).
| Category | Values |
|---|---|
| Attack types | BEC/Fraud, Callback Phishing, Credential Phishing |
| Tactics and techniques | Free email provider, Social engineering, Free file host |
Event coverage
| Message attribute |
|---|
| headers (collection) |
| headers.reply_to (collection) |
| sender.email |
| type |
Rule body MQL
type.inbound
and sender.email.email in (
'drive-shares-dm-noreply@google.com',
'drive-shares-noreply@google.com',
)
and not any(headers.reply_to, .email.domain.domain in $org_domains)
// the message needs to have a reply-to address
and length(headers.reply_to) > 0
// new reply-to
and any(headers.reply_to, network.whois(.email.domain).days_old < 30)
Detection logic
Scope: inbound message.
A Google Drive sharing notification containing a reply-to address from a recently registered domain (less than 30 days old). The reply-to domain does not match any organizational domains.
- inbound message
- sender.email.email in ('drive-shares-dm-noreply@google.com', 'drive-shares-noreply@google.com')
not:
any of
headers.reply_towhere:- .email.domain.domain in $org_domains
- length(headers.reply_to) > 0
any of
headers.reply_towhere:- network.whois(.email.domain).days_old < 30
Inspects: headers.reply_to, headers.reply_to[].email.domain, headers.reply_to[].email.domain.domain, sender.email.email, type.inbound. Sensors: network.whois. Reference lists: $org_domains.
Indicators matched (2)
| Field | Match | Value |
|---|---|---|
sender.email.email | member | drive-shares-dm-noreply@google.com |
sender.email.email | member | drive-shares-noreply@google.com |