Phishing: Spearphishing via Service T1566.003

Tactic: Initial Access

Adversaries may send spearphishing messages via third-party services in an attempt to gain access to victim systems. Spearphishing via service is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of third party services rather than directly via enterprise email channels.

Authoring guide

Patterns shared across the 1 rule above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (4 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
data_stream.dataset1eq 1microsoft_exchange_online_message_trace.log
email.from.address1eq 1azure-noreply@microsoft.com
email.subject1contains 1amount due, azure monitor alert, bank account
event.outcome1in 1success, unknown

Top indicator values (26 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
data_stream.dataseteq
microsoft_exchange_online_message_trace.log
1
email.from.addresseq
azure-noreply@microsoft.com
1
email.subjectcontains
amount due
1
email.subjectcontains
azure monitor alert
1
email.subjectcontains
bank account
1
email.subjectcontains
billing
1
email.subjectcontains
charge
1
email.subjectcontains
credit card
1
email.subjectcontains
financial
1
email.subjectcontains
funds
1
email.subjectcontains
inv-
1
email.subjectcontains
invoice
1
email.subjectcontains
order-
1
email.subjectcontains
overdue
1
email.subjectcontains
past due
1
email.subjectcontains
payment
1
email.subjectcontains
purchase
1
email.subjectcontains
receipt
1
email.subjectcontains
refund
1
email.subjectcontains
remittance
1
email.subjectcontains
renewal
1
email.subjectcontains
subscription
1
email.subjectcontains
transaction
1
email.subjectcontains
wire transfer
1
event.outcomein
success
138
event.outcomein
unknown
1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Elastic 1 rule