| ID | Name |
|---|---|
| T1090.001 | Internal Proxy |
| T1090.002 | External Proxy |
| T1090.003 | Multi-hop Proxy |
| T1090.004 | Domain Fronting |
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.
For example, adversaries may construct or use onion routing networks – such as the publicly available Tor network – to transport encrypted C2 traffic through a compromised population, allowing communication with any device within the network.[1] Adversaries may also use operational relay box (ORB) networks composed of virtual private servers (VPS), Internet of Things (IoT) devices, smart devices, and end-of-life routers to obfuscate their operations.[2]
In the case of network infrastructure, it is possible for an adversary to leverage multiple compromised devices to create a multi-hop proxy chain (i.e., Network Devices). By leveraging Patch System Image on routers, adversaries can add custom code to the affected network devices that will implement onion routing between those nodes. This method is dependent upon the Network Boundary Bridging method allowing the adversaries to cross the protected network boundary of the Internet perimeter and into the organization’s Wide-Area Network (WAN). Protocols such as ICMP may be used as a transport.
Similarly, adversaries may abuse peer-to-peer (P2P) and blockchain-oriented infrastructure to implement routing between a decentralized network of peers.[3]
| ID | Name | Description |
|---|---|---|
| G0007 | APT28 |
APT28 has routed traffic over Tor and VPN servers to obfuscate their activities.[4] |
| G0016 | APT29 |
A backdoor used by APT29 created a Tor hidden service to forward traffic from the Tor client to local ports 3389 (RDP), 139 (Netbios), and 445 (SMB) enabling full remote access from outside the network and has also used TOR.[5][6] |
| S0438 | Attor | |
| S1184 | BOLDMOVE |
BOLDMOVE is capable of relaying traffic from command and control servers to follow-on systems.[8] |
| C0004 | CostaRicto |
During CostaRicto, the threat actors used a layer of proxies to manage C2 communications.[9] |
| S0687 | Cyclops Blink |
Cyclops Blink has used Tor nodes for C2 traffic.[10] |
| S0281 | Dok | |
| S0384 | Dridex |
Dridex can use multiple layers of proxy servers to hide terminal nodes in its infrastructure.[12] |
| G1003 | Ember Bear |
Ember Bear has configured multi-hop proxies via ProxyChains within victim environments.[13] |
| G0085 | FIN4 | |
| C0053 | FLORAHOX Activity |
FLORAHOX Activity has routed traffic through a customized Tor relay network layer.[2] |
| S1144 | FRP |
The FRP client can be configured to connect to the server through a proxy.[15] |
| G0047 | Gamaredon Group |
Gamaredon Group has used Tor for C2 traffic.[16] |
| S0342 | GreyEnergy |
GreyEnergy has used Tor relays for Command and Control servers.[17] |
| G0100 | Inception |
Inception used chains of compromised routers to proxy C2 communications between them and cloud service providers.[18] |
| S0604 | Industroyer |
Industroyer used Tor nodes for C2.[19] |
| S0276 | Keydnap |
Keydnap uses a copy of tor2web proxy for HTTPS communications.[20] |
| S0641 | Kobalos |
Kobalos can chain together multiple compromised machines as proxies to reach their final targets.[21][22] |
| G0065 | Leviathan |
Leviathan has used multi-hop proxies to disguise the source of their malicious traffic.[23] |
| G0030 | Lotus Blossom |
Lotus Blossom has used tools such as the publicly available HTran tool for proxying traffic in victim environments.[24] |
| S0282 | MacSpy | |
| G1051 | Medusa Group |
Medusa Group has used TOR nodes for communications.[25][26][27] |
| S1106 | NGLite |
NGLite has abused NKN infrastructure for its C2 communication.[3] |
| S1100 | Ninja |
Ninja has the ability to use a proxy chain with up to 255 hops when using TCP.[28] |
| S1107 | NKAbuse |
NKAbuse has abused the NKN public blockchain protocol for its C2 communications.[29][30] |
| C0014 | Operation Wocao |
During Operation Wocao, threat actors executed commands through the installed web shell via Tor exit nodes.[31] |
| C0055 | Quad7 Activity |
Quad7 Activity has routed traffic through chains of compromised network devices for password spray attacks.[32] |
| C0056 | RedPenguin |
During RedPenguin, UNC3886 used infrastructure associated with operational relay box (ORB) networks.[33] |
| C0059 | Salesforce Data Exfiltration |
During Salesforce Data Exfiltration, threat actors used Tor IPs for voice calls and for the collection of stolen data.[34] |
| S0623 | Siloscape | |
| C0052 | SPACEHOP Activity |
SPACEHOP Activity has routed traffic through chains of compromised network devices to proxy C2 communications.[2] |
| S0491 | StrongPity |
StrongPity can use multiple layers of proxy servers to hide terminal nodes in its infrastructure.[36] |
| S0183 | Tor |
Traffic traversing the Tor network will be forwarded to multiple nodes before exiting the Tor network and continuing on to its intended destination.[37] |
| S0022 | Uroburos |
Uroburos can use implants on multiple compromised machines to proxy communications through its worldwide P2P network.[38] |
| S0386 | Ursnif | |
| G1017 | Volt Typhoon |
Volt Typhoon has used multi-hop proxies for command-and-control infrastructure.[41] |
| S0366 | WannaCry | |
| G0128 | ZIRCONIUM |
ZIRCONIUM 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.[2] |
| ID | Mitigation | Description |
|---|---|---|
| M1037 | Filter Network Traffic |
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. |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0359 | Multi-hop Proxy Behavior via Relay Node Chaining, Onion Routing, and Network Tunneling | AN1020 |
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. |
| AN1021 |
Tools such as |
||
| AN1022 |
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. |
||
| AN1023 |
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. |
||
| AN1024 |
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. |