Proxy: Internal Proxy

APT39 used custom tools to create SOCK5 and custom protocol proxies between infected hosts.^[2][3]

The "ZJ" variant of BACKSPACE allows "ZJ link" infections with Internet access to relay traffic from "ZJ listen" to a command server.^[4]

CHOPSTICK used a proxy server between victims and the C2 server.^[5]

Cobalt Strike can be configured to have commands relayed over a peer-to-peer network of infected hosts. This can be used to limit the number of egress points, or provide access to a host without direct internet access.^[6][7]

Drovorub can use a port forwarding rule on its agent module to relay network traffic through the client module to a remote host on the same network.^[8]

Duqu can be configured to have commands relayed over a peer-to-peer network of infected hosts if some of the hosts do not have Internet access.^[9]

FatDuke can used pipes to connect machines with restricted internet access to remote machines via other infected hosts.^[10]

FIN13 has utilized a proxy tool to communicate between compromised assets.^[11]

Higaisa discovered system proxy settings and used them if available.^[12]

Hikit supports peer connections.^[13]

InvisiMole can function as a proxy to create a server that relays communication between the client and C&C server, or between two clients.^[14]

Kazuar has used internal nodes on the compromised network for C2 communications.^[15]

Lazarus Group has used a compromised router to serve as a proxy between a victim network's corporate and restricted segments.^[16]

Mafalda can create a named pipe to listen for and send data to a named pipe-based C2 server.^[17]

metaMain can create a named pipe to listen for and send data to a named pipe-based C2 server.^[17]

MiniDuke can can use a named pipe to forward communications from one compromised machine with internet access to other compromised machines.^[10]

Mythic can leverage a peer-to-peer C2 profile between agents.^[18]

Ninja can proxy C2 communications including to and from internal agents without internet connectivity.^[19][20]

During Operation Wocao, threat actors proxied traffic through multiple infected systems.^[21]

Pay2Key has designated machines in the compromised network to serve as reverse proxy pivot points to channel communications with C2.^[22][23]

During the SolarWinds Compromise, APT29 used SSH port forwarding capabilities on public-facing systems, and configured at least one instance of Cobalt Strike to use a network pipe over SMB.^[24][25]

Strider has used local servers with both local network and Internet access to act as internal proxy nodes to exfiltrate data from other parts of the network without direct Internet access.^[26]

Stuxnet installs an RPC server for P2P communications.^[27]

Turla has compromised internal network systems to act as a proxy to forward traffic to C2.^[28]

Volt Typhoon has used the built-in netsh port proxy command to create proxies on compromised systems to facilitate access.^[29][30]

The Winnti for Windows HTTP/S C2 mode can make use of a local proxy.^[31]

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 C2 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.^[32]