Phishing for Information T1598

Tactic: Reconnaissance

Adversaries may send phishing messages to elicit sensitive information that can be used during targeting. Phishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Phishing for information is different from Phishing in that the objective is gathering data from the victim rather than executing malicious code.

Events covered

2 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 9 rules 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 (14 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
CommandLine2contains 2, in 1*\\AppData\\Local\\Microsoft\\Outlook\\*, *\\AppData\\Local\\Temp\\*, *\\Content.Outlook\\*, .htm, :\users\
ChannelCount1gt 13
Event1eq 1chat_message.sent
EventType1eq 1IntrusionEvent
Image1ends_with 1\brave.exe, \chrome.exe, \firefox.exe
Message1regex_match 1http(s?):\\/\\/
TriggerCount1eq 11
id.applicationName1eq 1gmail
parameters.message_info.is_spam1eq 1True
phishScore1ge 190
quarantineFolder1eq 1Phish
quarantineRule1eq 1phish
sourcetype1eq 1cisco:sfw:estreamer
threatsInfoMap1array_any 1

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
ChannelCountgt
3
1
CommandLinecontains
.htm
1
CommandLinecontains
.rdp
1
CommandLinecontains
:\users\
16
CommandLinecontains
\downloads\
114
CommandLinein
*\\AppData\\Local\\Microsoft\\Outlook\\*
1
CommandLinein
*\\AppData\\Local\\Temp\\*
12
CommandLinein
*\\Content.Outlook\\*
1
CommandLinein
*\\Downloads\\*
1
CommandLinein
*\\Olk\\Attachments\\*
1
Eventeq
chat_message.sent
1
EventTypeeq
IntrusionEvent
118
Imageends_with
\brave.exe
111
Imageends_with
\chrome.exe
113
Imageends_with
\firefox.exe
16
Imageends_with
\msedge.exe
114
Imageends_with
\opera.exe
111
Imageends_with
\vivaldi.exe
111
Messageregex_match
http(s?):\\/\\/
1
TriggerCounteq
1
1
id.applicationNameeq
gmail
17
parameters.message_info.is_spameq
True
13
phishScorege
90
1
quarantineFoldereq
Phish
1
quarantineRuleeq
phish
1
sourcetypeeq
cisco:sfw:estreamer
132

Exclusions (1 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
actor.emailcontains
/hd/domain/
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)

Sigma 1 rule

Splunk 2 rules

Kusto 3 rules

Panther 3 rules