EXPLORE
← Back to Explore
sublimemediumRule

Service abuse: Google Drive share from an unsolicited reply-to address

Identifies messages appearing to come from Google Drive sharing notifications that contain a reply-to address not previously seen in organizational communications. This tactic exploits trust in legitimate Google services while attempting to establish unauthorized communication channels.

Detection Query

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)

//
// This rule makes use of a beta feature and is subject to change without notice
// using the beta feature in custom rules is not suggested until it has been formally released
//

// reply-to address has never sent an email to the org
and beta.profile.by_reply_to().prevalence == "new"

// reply-to email address has never been sent an email by the org
and not beta.profile.by_reply_to().solicited

// do not match if the reply_to address has been observed as a reply_to address
// of a message that has been classified as benign
and not beta.profile.by_reply_to().any_messages_benign

Data Sources

Email MessagesEmail HeadersEmail Attachments

Platforms

email

Tags

Attack surface reduction
Raw Content
name: "Service abuse: Google Drive share from an unsolicited reply-to address"
description: "Identifies messages appearing to come from Google Drive sharing notifications that contain a reply-to address not previously seen in organizational communications. This tactic exploits trust in legitimate Google services while attempting to establish unauthorized communication channels."
type: "rule"
severity: "medium"
source: |
  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)

  //
  // This rule makes use of a beta feature and is subject to change without notice
  // using the beta feature in custom rules is not suggested until it has been formally released
  //
  
  // reply-to address has never sent an email to the org
  and beta.profile.by_reply_to().prevalence == "new"
  
  // reply-to email address has never been sent an email by the org
  and not beta.profile.by_reply_to().solicited

  // do not match if the reply_to address has been observed as a reply_to address
  // of a message that has been classified as benign
  and not beta.profile.by_reply_to().any_messages_benign

tags:
 - "Attack surface reduction"
attack_types:
  - "BEC/Fraud"
  - "Callback Phishing"
  - "Credential Phishing"
tactics_and_techniques:
  - "Free email provider"
  - "Social engineering"
  - "Free file host"
detection_methods:
  - "Header analysis"
  - "Sender analysis"
id: "4581ec0c-aed2-50ed-8e16-2c9ca1d350ff"