Has utilized email notifications from malware distribution servers to track victim engagement.1
Mail Protocols T1071.003
- Tactic
- Command and Control
- Platforms
- Linux, macOS, Network Devices, Windows
- Version
- 1.2
- Created
- 15 March 2020
- Last modified
- 24 October 2025
- Contributor
- Don Le, Stifel Financial
Adversaries may communicate using application layer protocols associated with electronic mail delivery to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.
Mail Protocols MITRE reference T1071.003
6 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used e-mail to send exfiltrated data to C2 servers.1
Uses SMTP for C2 communications.1
Has used multiple backdoors which communicate with a C2 server via email attachments.1
Has used IMAP, POP3, and SMTP for a communication channel in various implants, including using self-registered Google Mail accounts and later compromised email servers of its victims.12
All 6 groups for this technique
20 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can receive and send back the results of executed C2 commands through email.1
Uses the IMAP email protocol for command and control purposes.1
Can communicates with C2 using email messages via the Outlook Messaging API (MAPI).1
Can use emails for C2 communications.1
Can use email attachments for C2 communications.1
All 20 software entries for this technique · 6 newest in this preview
Offense vs defense T1071.003
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Mail Protocols detection strategy DET0135
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Mail Protocol-Based C2 Activity (SMTP, IMAP, POP3)
AN0379 · Windows
Detects unauthorized use of SMTP/IMAP/POP3 by suspicious binaries (e.g., PowerShell, rundll32) to exfiltrate data or beacon via email, often bypassing proxy or content filters.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
| Network Traffic ContentDC0085 | NSM:Flow | smtp.log |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ProcessImageName | Limit to uncommon clients (e.g., scripts or CLI tools using .NET SMTP libraries) |
| DestPortFilter | Typically 25, 587, 993, 995, or 465 – flag anomalies |
| AttachmentType | Flag suspicious attachments (e.g., .zip, .7z, .bin) |
AN0380 · Linux
Detects non-interactive or script-driven email transmission using tools like sendmail, mailx, or custom SMTP scripts by background processes, especially when sending attachments or large payloads.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| Network Traffic ContentDC0085 | NSM:Flow | smtp.log, conn.log |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TransferSizeThreshold | Bytes transferred via SMTP session |
| ScriptNameFilter | e.g., base64 encoded mailer scripts or one-liners in cron |
AN0381 · macOS
Detects email-sending behavior via Terminal, AppleScript, or Automator that interfaces with SMTP or IMAP, typically using curl or mail-related APIs in unsanctioned contexts.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | macos:unifiedlog | log stream --predicate 'processImagePath CONTAINS "curl" OR "osascript"' |
| Network Traffic FlowDC0078 | macos:osquery | socket_events |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserContext | Monitor non-mail client users initiating SMTP/IMAP |
| TimeWindow | Look for execution of mail commands during off-hours |
AN0382 · Network Devices
Detects hosts transmitting large volumes of SMTP, IMAP, or POP3 traffic to external IPs or relays that aren't associated with the enterprise mail infrastructure.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Traffic ContentDC0085 | NSM:Flow | smtp.log, conn.log |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ExternalMailRelayFilter | Dest IPs not matching sanctioned SMTP/IMAP relays |
| OutflowToInflowRatio | Outbound email bytes vastly exceed response |
Limit the ability of servers and critical systems to initiate outbound email communications. Filtering SMTP/IMAP/POP3 traffic to only trusted mail servers reduces the risk of attackers using compromised systems to exfiltrate data via email or to receive commands from attacker-controlled email accounts.
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate activity at the network level.