- Tactic
- Command and Control
- Platforms
- ESXi, Linux, macOS, Network Devices, Windows
- Version
- 2.4
- Created
- 14 March 2020
- Last modified
- 12 May 2026
- Contributor
- Eduardo Chavarro Ovalle
Adversaries may chain together multiple proxies to disguise the source of malicious traffic. Typically, a defender will be able to identify the last proxy traffic traversed before it enters their network; the defender may or may not be able to identify any previous proxies before the last-hop proxy. This technique makes identifying the original source of the malicious traffic even more difficult by requiring the defender to trace malicious traffic through several proxies to identify its source.
Multi-hop Proxy MITRE reference T1090.003
12 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 multi-hop proxies for command-and-control infrastructure.1
Has configured multi-hop proxies via ProxyChains within victim environments.1
Has utilized an ORB (operational relay box) network – consisting compromised devices such as small office and home office (SOHO) routers, IoT devices, and leased virtual private servers (VPS) – to proxy traffic.1
Used chains of compromised routers to proxy C2 communications between them and cloud service providers.1
All 12 groups for this technique · 6 newest in this preview
8 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the 2025 Poland Wiper Attacks, the adversaries utilized Tor nodes for C2.1
During RedPenguin, UNC3886 used infrastructure associated with operational relay box (ORB) networks.1
Has routed traffic through chains of compromised network devices for password spray attacks.1
During CostaRicto, the threat actors used a layer of proxies to manage C2 communications.1
Has routed traffic through a customized Tor relay network layer.1
Has routed traffic through chains of compromised network devices to proxy C2 communications.1
All 8 campaigns for this technique · 6 newest in this preview
23 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 the ability to exfiltrate stolen credentials via the Session messenger network.1
Has used multiple proxy layers, such as SOCKS5 and Tor, for C2 communication.1234 SystemBC has also leveraged Tor for encrypting and concealing C2 traffic.2 The server component of SystemBC has used SOCKS5 for C2 communication.3
Is capable of relaying traffic from command and control servers to follow-on systems.1
The FRP client can be configured to connect to the server through a proxy.1
Has abused the NKN public blockchain protocol for its C2 communications.12
Has abused NKN infrastructure for its C2 communication.1
All 23 software entries for this technique · 6 newest in this preview
Offense vs defense T1090.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.
Multi-hop Proxy detection strategy DET0359
MITRE names one behaviour worth catching for this technique and breaks it into 5 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Multi-hop Proxy Behavior via Relay Node Chaining, Onion Routing, and Network Tunneling
AN1020 · Windows
Suspicious processes (e.g., Tor clients, relays, unknown binaries) launch with sustained encrypted outbound traffic to known anonymity infrastructure (e.g., Tor, I2P), and may relay to additional internal systems via reverse proxying, ICMP tunneling, or socket forwarding.
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 Traffic FlowDC0078 | dns:query | Outbound resolution to hidden service domains (e.g., `.onion`) |
| 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 |
|---|---|
| DomainCategory | Can be tuned to .onion, I2P, or suspicious CDN domains. |
| ProcessParent | Detect known-good vs. abnormal launching binaries (e.g., mshta spawning Tor). |
| ConnectionDuration | Threshold for persistent connections over known relay ports (e.g., 9050). |
AN1021 · Linux
Tools such as tor, nglite, proxychains, chisel, or custom daemons repeatedly initiate outbound sessions to multiple nodes before final destination. This behavior is abnormal for Linux services outside of VPN, monitoring, or CDN relay 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 | auditd:SYSCALL | execve for proxy tools |
| Network Traffic FlowDC0078 | NSM:Flow | conn.log + ssl.log with Tor fingerprinting |
| Network Traffic ContentDC0085 | Netfilter/iptables | Forwarded packets 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 |
|---|---|
| ExecutablePath | Match known proxy tools, tuned for environment. |
| RelayCount | Detect outbound chaining behavior through >2 IPs in short succession. |
| ProtocolType | Allow filtering by ICMP, TCP/443, UDP for obfuscation channels. |
AN1022 · macOS
LaunchAgents or LaunchDaemons initiate persistent Tor or relay processes that make encrypted outbound connections. May be paired with sandbox bypasses or unsigned executables communicating over SOCKS proxies.
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 | process, socket, and DNS logs |
| Network Traffic FlowDC0078 | macos:unifiedlog | forwarded encrypted traffic |
| Network Connection CreationDC0082 | macos:osquery | process_events + launchd |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| LaunchdLabel | Regex for masking patterns in LaunchAgents with proxy behavior. |
| UnsignedBinary | Allow for exceptions for known unsigned binaries. |
| SOCKSPortUsage | Monitor local 9050/9150 activity and rerouted system traffic. |
AN1023 · ESXi
Outbound encrypted traffic initiated from hypervisor shell or via VM backdoor mechanisms to relays in VPS infrastructure, especially if traversing multiple nodes before reaching Internet destination. Packet captures or firewall logs show non-VM communication paths.
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:vmkernel | /var/log/vmkernel.log |
| Network Connection CreationDC0082 | esxi:esxupdate | /var/log/esxupdate.log or /var/log/vmksummary.log |
| Network Traffic ContentDC0085 | NSM:Flow | Relay patterns across IP hops |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| HopCount | Threshold on number of IPs contacted in sequence without DNS resolution. |
| ShellAccess | Flag if relay communication initiated by ESXi shell or unknown VM agent. |
| VPSIPRange | Filter for known Tor/VPS egress networks. |
AN1024 · Network Devices
Encrypted traffic or ICMP tunneling from border routers to internal routers or unknown external IPs. Forwarded traffic shows consistent hop-to-hop relaying without matching configured VPN or expected network topology.
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 |
|---|---|---|
| Firmware ModificationDC0004 | networkdevice:syslog | Custom firmware or routing changes |
| Network Traffic FlowDC0078 | NSM:Flow | Relayed session pathing (multi-hop) |
| Network Traffic ContentDC0085 | NSM:Firewall | Outbound encrypted traffic |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| VPNConfigWhitelist | Define allowed internal router communication paths. |
| ICMPPayloadEntropy | High entropy ICMP payloads may indicate tunneling activity. |
| RelayChainSignature | Track known multi-hop pattern signatures or port hopping techniques. |
Traffic to known anonymity networks and C2 infrastructure can be blocked through the use of network allow and block lists. It should be noted that this kind of blocking may be circumvented by other techniques like Domain Fronting.
Tests from Atomic Red Team (MIT licence) · technique definition