Has employed layers of redundancy to maintain access to compromised environments including network devices, hypervisors, and virtual machines.1
Fallback Channels T1008
- Tactic
- Command and Control
- Platforms
- ESXi, Linux, macOS, Windows
- Version
- 1.1
- Created
- 31 May 2017
- Last modified
- 12 May 2026
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
Fallback Channels MITRE reference T1008
5 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.
Used the Steam community page as a fallback mechanism for C2.1
Malware ISMAgent falls back to its DNS tunneling mechanism if it is unable to reach the C2 server over HTTP.1
FIN7's Harpy backdoor malware can use DNS as a backup channel for C2 if HTTP fails.1
Malware SierraAlfa sends data to one of the hard-coded C2 servers chosen at random, and if the transmission fails, chooses a new C2 server to attempt the transmission again.12
All 5 groups for this technique
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During Night Dragon, threat actors used company extranet servers as secondary C2 servers.1
All 1 campaigns for this technique
51 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 established Fallback Channels to exfiltrate data to Github when other configured infrastructure is found to be unreachable.1234
Can compress and encrypt data and exfiltrate it via POST to an attacker-controlled domain. If that method fails it can use the victim's own GitHub account to create a public repository and uploads the encrypted data as a release asset.12345
Can use active and passive C2 modes that use different encryption algorithms and backdoor commands.1
Can use a backup channel to request a new refresh token from its C2 server after 10 consecutive unsuccessful connections to the primary OneDrive C2 server.1
Can attempt to connect to a second hard-coded C2 if the first hard-coded C2 address fails.1
All 51 software entries for this technique · 6 newest in this preview
Offense vs defense T1008
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.
Fallback Channels detection strategy DET0499
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.
Behavioral Detection of Fallback or Alternate C2 Channels
AN1376 · Windows
Establishing network connections on uncommon ports or protocols following C2 disruption or blocking. Often executed by processes that typically exhibit no network activity.
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 FlowDC0078 | NSM:Flow | uncommon ports |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| DestinationPort | Can be tuned to include unexpected or high-entropy ports not typically associated with the process. |
| ProcessName | Useful to filter benign applications vs suspicious fallback attempts. |
| DataVolumeRatio | Tunable ratio of sent/received bytes to indicate potential C2 beaconing or exfiltration. |
| TimeWindow | Adjust temporal window to match likely fallback C2 retries after primary channel fails. |
AN1377 · Linux
Creation of outbound connections on alternate ports or using covert transport (e.g., ICMP, DNS) from non-network-intensive processes, following known disruption or blocked traffic.
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 FlowDC0078 | NSM:Flow | alternate ports |
| Network Connection CreationDC0082 | auditd:SYSCALL | outbound connections |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ProtocolType | Can filter for rare fallback channel types (e.g., ICMP, DNS over HTTP). |
| UserContext | Tuning by user (e.g., root vs. service account) helps suppress noise. |
AN1378 · macOS
Outbound fallback traffic from low-profile or background launch agents using unusual protocols or destinations after primary channel inactivity.
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 FlowDC0078 | NSM:Flow | None |
| Network Connection CreationDC0082 | macos:unifiedlog | None |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| LaunchAgentContext | Used to suppress known legitimate agents. |
| PayloadEntropy | Can help isolate covert or encrypted fallback traffic. |
AN1379 · ESXi
Outbound traffic from host management services or guest-to-host interactions over unusual interfaces (e.g., backdoor API endpoints or external VPN tunnels).
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 FlowDC0078 | esxi:vpxd | None |
| Network Connection CreationDC0082 | esxi:vmkernel | None |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| InterfaceName | May vary based on ESXi build and should be filtered to suppress known interfaces. |
| FallbackIPRanges | Environment-specific ranges to ignore (e.g., DR tunnels or out-of-band mgmt). |
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 protocol used by a particular adversary or tool, and will likely be different across various malware families and versions. Adversaries will likely change tool C2 signatures over time or construct protocols in such a way as to avoid detection by common defensive tools.