ATT&CKProcedure examples

Procedure examples

Real-world descriptions of how a group, tool or campaign used a technique.

11362 examples

TechniqueUsed byProcedure example
T1071.001
Web Protocols
MalwareELMER

ELMER uses HTTP for command and control.

T1071.001
Web Protocols
MalwarePolyglotDuke

PolyglotDuke has has used HTTP GET requests in C2 communications.

T1071.001
Web Protocols
MalwareHexEval Loader

HexEval Loader has used HTTP and HTTPS POST requests to communicate with C2.

T1071.001
Web Protocols
MalwareAuTo Stealer

AuTo Stealer can use HTTP to communicate with its C2 servers.

T1071.001
Web Protocols
MalwareShrinkLocker

ShrinkLocker uses HTTP POST requests to communicate victim information back to the threat actor.

T1071.001
Web Protocols
MalwareFlawedAmmyy

FlawedAmmyy has used HTTP for C2.

T1071.001
Web Protocols
MalwareCuckoo Stealer

Cuckoo Stealer can use the curl API for C2 communications.

T1071.001
Web Protocols
MalwareGuLoader

GuLoader can use HTTP to retrieve additional binaries.

T1071.001
Web Protocols
MalwareInvisiMole

InvisiMole uses HTTP for C2 communications.

T1071.001
Web Protocols
MalwareP.A.S. Webshell

P.A.S. Webshell can issue commands via HTTP POST.

T1071.001
Web Protocols
MalwareWhisperGate

WhisperGate can make an HTTPS connection to download additional files.

T1071.001
Web Protocols
MalwareZeroT

ZeroT has used HTTP for C2.

T1071.001
Web Protocols
MalwareKeydnap

Keydnap uses HTTPS for command and control.

T1071.001
Web Protocols
MalwareRDAT

RDAT can use HTTP communications for C2, as well as using the WinHTTP library to make requests to the Exchange Web Services API.

T1071.001
Web Protocols
MalwareOkrum

Okrum uses HTTP for communication with its C2.

T1071.001
Web Protocols
MalwareTRANSLATEXT

TRANSLATEXT has used HTTP to communicate with the C2 server.

T1071.001
Web Protocols
MalwareRegin

The Regin malware platform supports many standard protocols, including HTTP and HTTPS.

T1071.001
Web Protocols
MalwareLine Dancer

Line Dancer uses HTTP POST requests to interact with compromised devices.

T1071.001
Web Protocols
MalwareNeoichor

Neoichor can use HTTP for C2 communications.

T1071.001
Web Protocols
MalwareRaspberry Robin

Raspberry Robin uses outbound HTTP requests containing victim information for retrieving second stage payloads. Variants of Raspberry Robin can download archive files (such as 7-Zip files) via the victim web browser for second stage execution.

T1071.001
Web Protocols
MalwareDiavol

Diavol has used HTTP GET and POST requests for C2.

T1071.001
Web Protocols
MalwareDoki

Doki has communicated with C2 over HTTPS.

T1071.001
Web Protocols
MalwareRustyWater

RustyWater has used the Rust request library for HTTP C2 communication.

T1071.001
Web Protocols
MalwareIcedID

IcedID has used HTTPS in communications with C2.

T1071.001
Web Protocols
MalwareVERMIN

VERMIN uses HTTP for C2 communications.

T1071.001
Web Protocols
MalwareUBoatRAT

UBoatRAT has used HTTP for C2 communications.

T1071.001
Web Protocols
MalwareHTTPTroy

HTTPTroy has used HTTP POST requests to communicate with C2.

T1071.001
Web Protocols
MalwareMarkiRAT

MarkiRAT can initiate communication over HTTP/HTTPS for its C2 server.

T1071.001
Web Protocols
MalwarePowerShower

PowerShower has sent HTTP GET and POST requests to C2 servers to send information and receive instructions.

T1071.001
Web Protocols
MalwareKazuar

Kazuar uses HTTP and HTTPS to communicate with the C2 server. Kazuar can also act as a webserver and listen for inbound HTTP requests through an exposed API.

T1071.001
Web Protocols
MalwareDarkComet

DarkComet can use HTTP for C2 communications.

T1071.001
Web Protocols
MalwareNETEAGLE

NETEAGLE will attempt to detect if the infected host is configured to a proxy. If so, NETEAGLE will send beacons via an HTTP POST request. NETEAGLE will also use HTTP to download resources that contain an IP address and Port Number pair to connect to for further C2.

T1071.001
Web Protocols
MalwareCHIMNEYSWEEP

CHIMNEYSWEEP can send `HTTP GET` requests to  C2.

T1071.001
Web Protocols
MalwareFatDuke

FatDuke can be controlled via a custom C2 protocol over HTTP.

T1071.001
Web Protocols
MalwareBlackEnergy

BlackEnergy communicates with its C2 server over HTTP.

T1071.001
Web Protocols
MalwareDRATzarus

DRATzarus can use HTTP or HTTPS for C2 communications.

T1071.001
Web Protocols
MalwareRising Sun

Rising Sun has used HTTP and HTTPS for command and control.

T1071.001
Web Protocols
MalwareShimRat

ShimRat communicated over HTTP and HTTPS with C2 servers.

T1071.001
Web Protocols
MalwareFlagpro

Flagpro can communicate with its C2 using HTTP.

T1071.001
Web Protocols
MalwareHi-Zor

Hi-Zor communicates with its C2 server over HTTPS.

T1071.001
Web Protocols
MalwareChina Chopper

China Chopper's server component executes code sent via HTTP POST commands.

T1071.001
Web Protocols
MalwareSnappyTCP

SnappyTCP connects to the command and control server via a TCP socket using HTTP.

T1071.001
Web Protocols
MalwareLightSpy

LightSpy's C2 communication is performed over WebSockets using the open source library SocketRocket with functionality such as, heartbeat, receiving commands, and updating command status.

T1071.001
Web Protocols
MalwarePUNCHBUGGY

PUNCHBUGGY enables remote interaction and can obtain additional code over HTTPS GET and POST requests.

T1071.001
Web Protocols
MalwareGoldMax

GoldMax has used HTTPS and HTTP GET requests with custom HTTP cookies for C2.

T1071.001
Web Protocols
MalwareLIGHTWIRE

LIGHTWIRE can use HTTP for C2 communications.

T1071.001
Web Protocols
MalwareMiniDuke

MiniDuke uses HTTP and HTTPS for command and control.

T1071.001
Web Protocols
MalwareHyperBro

HyperBro has used HTTPS for C2 communications.

T1071.001
Web Protocols
MalwareAnchor

Anchor has used HTTP and HTTPS in C2 communications.

T1071.001
Web Protocols
MalwareLine Runner

Line Runner utilizes an HTTP-based Lua backdoor on victim machines.

Data from MITRE ATT&CK® (Enterprise). ATT&CK® is a registered trademark of The MITRE Corporation.