Malware has exfiltrated collected data via Telegram bot C2 channels using encrypted communications.1
Exfiltration Over C2 Channel T1041
- Tactic
- Exfiltration
- Platforms
- ESXi, Linux, macOS, Windows
- Version
- 2.3
- Created
- 31 May 2017
- Last modified
- 12 May 2026
- Contributor
- William Cain
Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.
Exfiltration Over C2 Channel MITRE reference T1041
27 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 exfiltrated data from a compromised host to actor-controlled C2 servers.12345678910
Transmitted collected victim host information via HTTP POST to command and control infrastructure.1
Delivered a PowerShell script capable of recursively scanning victim machines looking for various file types before exfiltrating identified files via HTTP.1
Exfiltrated staged data using tools such as Putty and WinSCP, communicating with command and control servers.1
Has exfiltrated data from compromised VMware vCenter servers through an established C2 channel using the Teleport remote access tool.1
All 27 groups for this technique · 6 newest in this preview
10 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During SharePoint ToolShell Exploitation, threat actors exfiltrated stolen credentials and internal data over HTTPS to C2 infrastructure.1
During RedPenguin, UNC3886 uploaded specified files from compromised devices to a remote server. 1
Included use of existing command and control channels for data exfiltration.12
Leviathan exfiltrated collected data over existing command and control channels during Leviathan Australian Intrusions.1
During C0017, APT41 used its Cloudflare services C2 channels for data exfiltration.1
During HomeLand Justice, threat actors used HTTP to transfer data from compromised Exchange servers.1
All 10 campaigns for this technique · 6 newest in this preview
166 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.
Has exfiltrated collected data to typosquat C2 domains including scan.aquasecurtiy[.]org.1234
Can exfiltrate collected system information and documents to C2.12
Has uploaded files to the C2 server. Additionally, MuddyViper has the ability to upload the specified file in chunks with sleep time between each chunk.1
Has exfiltrated reconnaissance data on targeted systems to C2 servers.1
Can exfiltrate collected credentials and browser cookies to the C2 server.1
All 166 software entries for this technique · 6 newest in this preview
Offense vs defense T1041
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.
Exfiltration Over C2 Channel detection strategy DET0348
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 Strategy for Exfiltration Over C2 Channel
AN0988 · Windows
Identifies suspicious outbound traffic volume mismatches from processes that typically do not generate network activity, particularly over C2 protocols like HTTPS, DNS, or custom TCP/UDP ports, following file or data access.
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 |
| File AccessDC0055 | WinEventLog:Security | EventCode=4663, 4670, 4656 |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
| Network Traffic ContentDC0085 | NSM:Flow | Flow/PCAP analysis for outbound payloads |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| DataVolumeThreshold | Set threshold for outbound transfer size exceeding typical C2 traffic (e.g., >1MB in <5min). |
| KnownBenignProcesses | List of approved processes that may exhibit high outbound traffic (e.g., updates). |
AN0989 · Linux
Monitors for processes reading sensitive files then immediately initiating unusual outbound connections or bulk transfer sessions over persistent sockets, particularly with encrypted or binary 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 FlowDC0078 | NSM:Flow | session stats with bytes_out > bytes_in |
| Network Connection CreationDC0082 | auditd:SYSCALL | connect |
| Network Traffic ContentDC0085 | NSM:Flow | conn.log + files.log + ssl.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 |
|---|---|
| OutboundEntropyScore | Threshold for high-entropy payloads indicative of encoded or encrypted exfil data. |
| ConnectionDuration | Defines length of time over which transfer size must be aggregated to trigger detection. |
AN0990 · macOS
Detects unauthorized applications or scripts accessing sensitive data followed by establishing encrypted outbound communication to rare external destinations or with abnormal byte ratios.
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:osquery | process_events |
| Network Traffic FlowDC0078 | macos:osquery | socket_events |
| Network Traffic ContentDC0085 | macos:unifiedlog | eventMessage = 'open', 'sendto', 'connect' |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ParentProcessAncestry | Enables defenders to tune legitimate vs. suspicious lineage (e.g., launchd → curl is uncommon). |
| ProtocolList | Focus detection on unusual protocols (e.g., IRC, FTP, DNS over HTTPS). |
AN0991 · ESXi
Detects VMs sending outbound traffic through non-standard services or to unknown destinations. Exfiltration over reverse shells tunneled via VMkernel or custom payloads routed via hostd/vpxa.
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 |
|---|---|---|
| File AccessDC0055 | esxi:syslog | guest OS outbound transfer logs |
| Network Traffic FlowDC0078 | esxi:vpxa | connection attempts and data transmission logs |
| Network Traffic ContentDC0085 | esxi:vmkernel | network stack module logs |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| GuestOSAllowList | Limit detection to sensitive or externally-exposed VMs handling confidential data. |
| TransferSizeThresholdMB | Minimum outbound transfer size before flagging anomalous C2-based exfiltration. |
| ProtocolAllowList | Define expected protocols for outbound data (e.g., disallow FTP/SCP over high ports). |
Data loss prevention can detect and block sensitive data being sent over unencrypted protocols.
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. Signatures are often for unique indicators within protocols and may be based on the specific obfuscation technique used by a particular adversary or tool, and will likely be different across various malware families and versions. Adversaries will likely change tool command and control signatures over time or construct protocols in such a way to avoid detection by common defensive tools.
Tests from Atomic Red Team (MIT licence) · technique definition