Procedure examples

Some TrickBot samples have used HTTP over ports 447 and 8082 for C2. Newer versions of TrickBot have been known to use a custom communication protocol which sends the data unencrypted over port 443.

Pikabot uses non-standard ports, such as 2967, 2223, and others, for HTTPS command and control communication.

RotaJakiro uses a custom binary protocol over TCP port 443.

Sardonic has the ability to connect with actor-controlled C2 servers using a custom binary protocol over port 443.

RedLeaves can use HTTP over non-standard ports, such as 995, for C2.

GravityRAT has used HTTP over a non-standard port, such as TCP port 46769.

InvisibleFerret has been observed utilizing HTTP communications to the C2 server over ports 1224, 2245 and 8637.

Bankshot binds and listens on port 1058 for HTTP traffic while also utilizing a FakeTLS method.

StrongPity has used HTTPS over port 1402 in C2 communication.

Hannotog uses non-standard listening ports, such as UDP 5900, for command and control purposes.

Emotet has used HTTP over ports such as 20, 22, 443, 7080, and 50000, in addition to using ports commonly associated with HTTP/S.

The server component of SystemBC has used various TCP ports for C2 communication.

PingPull can use HTTPS over port 8080 for C2.

SUGARUSH has used port 4585 for a TCP connection to its C2.

HOPLIGHT has connected outbound over TCP port 443 with a FakeTLS method.

Raspberry Robin will communicate via HTTP over port 8080 for command and control traffic.

BeaverTail has communicated with C2 IP addresses over ports 1224 or 1244.

PlugX has used random, high-number, non-standard ports to listen for subsequent actions and C2 activities.

TYPEFRAME has used ports 443, 8080, and 8443 with a FakeTLS method.

VIRTUALPIE has created listeners on hard coded TCP port 546.

BendyBear has used a custom RC4 and XOR encrypted protocol over port 443 for C2.

GlassWorm has distributed C2 using BitTorrent’s Distributed Hash Table (DHT) network to harness a decentralized command capability.

Metamorfo has communicated with hosts over raw TCP on port 9999.

RTM used Port 44443 for its VNC module.

Derusbi has used unencrypted HTTP on port 443 for C2.

WellMail has been observed using TCP port 25, without using SMTP, to leverage an open port for secure command and control communications.

BADCALL communicates on ports 443 and 8000 with a FakeTLS method.

MoonWind communicates over ports 80, 443, 53, and 8080 via raw sockets instead of the protocols usually associated with the ports.

HiddenFace's passive mode listens on TCP 47000.

OSX_OCEANLOTUS.D has used a custom binary protocol over TCP port 443 for C2.

Cyclops Blink can use non-standard ports for C2 not typically associated with HTTP or HTTPS traffic.

GoldenSpy has used HTTP over ports 9005 and 9006 for network traffic, 9002 for C2 requests, 33666 as a WebSocket, and 8090 to download files.

HARDRAIN binds and listens on port 443 with a FakeTLS method.

MacMa has used TCP port 5633 for C2 Communication.

PoetRAT used TLS to encrypt communications over port 143

ZxShell can use ports 1985 and 1986 in HTTP/S communication.

SPAWNCHIMERA has the ability to bind on a localhost and listen on port 8300.

njRAT has used port 1177 for HTTP C2 communications.

VIRTUALPITA has created listeners on hard coded TCP ports such as 2233, 7475, and 18098.

Covenant listeners and controllers can be configured to use non-standard ports.

QuasarRAT can use port 4782 on the compromised host for TCP callbacks.