Cross-source coverage
T1598.002 / ATT&CK
Phishing for Information: Spearphishing Attachment
2 rules across 2 sources.
From MITRE ATT&CK 19.2
Adversaries may send spearphishing messages with a malicious attachment to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: Establish Accounts or Compromise Accounts) and/or sending multiple, seemingly urgent messages.
All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email. In some cases, they may rely upon the recipient populating information, then returning the file. The text of the spearphishing email usually tries to give a plausible reason why the file should be filled-in, such as a request for information from a business associate. In other cases, adversaries may leverage techniques such as HTML Smuggling to harvest user credentials via fake login portals.
Adversaries may also use information from previous reconnaissance efforts (ex: Search Open Websites/Domains or Search Victim-Owned Websites) to craft persuasive and believable lures.
- Tactics
- Reconnaissance
- Platforms
- PRE
- Telemetry
-
Network TrafficApplication Log
How MITRE says to detect it DET0865
Detection of Spearphishing Attachment
PRE Analytic 1997
Monitor network data for uncommon data flows. Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed. Monitor and analyze traffic patterns and packet inspection associated to protocol(s) that do not follow the expected protocol standards and traffic flows (e.g extraneous packets that do not belong to established flows, gratuitous or anomalous traffic patterns, anomalous syntax, or structure). Consider correlation with process monitoring and command line to detect anomalous processes execution and command line arguments associated to traffic patterns (e.g. monitor anomalies in use of files that do not normally initiate connections for respective protocol(s)).
Network TrafficNoneApplication LogNoneNetwork TrafficNone
SigmaHQ/sigma
1 rule| Detection | Severity | Format |
|---|---|---|
| HTML File Opened From Download Folder | Low | Sigma |
splunk/security_content
1 rule| Detection | Severity | Format |
|---|---|---|
| Windows RDP File Execution | Undefined | SPL |