prompt
stringclasses
508 values
procedure
stringlengths
20
478
Application Layer Protocol:Web Protocols
OwaAuth uses incoming HTTP requests with a username keyword and commands and handles them as instructions to perform actions.
Application Layer Protocol:Web Protocols
P.A.S. Webshell can issue commands via HTTP POST.
Application Layer Protocol:Web Protocols
Pandora can communicate over HTTP.
Application Layer Protocol:Web Protocols
PcShare has used HTTP for C2 communication.
Application Layer Protocol:Web Protocols
Peppy can use HTTP to communicate with C2.
Application Layer Protocol:Web Protocols
PinchDuke transfers files from the compromised host via HTTP or HTTPS to a C2 server.
Application Layer Protocol:Web Protocols
A PingPull variant can communicate with its C2 servers by using HTTPS.
Application Layer Protocol:Web Protocols
PLEAD has used HTTP for communications with command and control (C2) servers.
Application Layer Protocol:Web Protocols
PlugX can be configured to use HTTP for command and control.
Application Layer Protocol:Web Protocols
pngdowner uses HTTP for command and control.
Application Layer Protocol:Web Protocols
PoetRAT has used HTTP and HTTPs for C2 communications.
Application Layer Protocol:Web Protocols
PolyglotDuke has has used HTTP GET requests in C2 communications.
Application Layer Protocol:Web Protocols
Pony has sent collected information to the C2 via HTTP POST request.
Application Layer Protocol:Web Protocols
PoshC2 can use protocols like HTTP/HTTPS for command and control traffic.
Application Layer Protocol:Web Protocols
PowerShower has sent HTTP GET and POST requests to C2 servers to send information and receive instructions.
Application Layer Protocol:Web Protocols
POWERTON has used HTTP/HTTPS for C2 traffic.
Application Layer Protocol:Web Protocols
PowGoop can send HTTP GET requests to malicious servers.
Application Layer Protocol:Web Protocols
POWRUNER can use HTTP for C2 communications.
Application Layer Protocol:Web Protocols
Proxysvc uses HTTP over SSL to communicate commands with the control server.
Application Layer Protocol:Web Protocols
Psylo uses HTTPS for C2.
Application Layer Protocol:Web Protocols
Pteranodon can use HTTP for C2.
Application Layer Protocol:Web Protocols
PUNCHBUGGY enables remote interaction and can obtain additional code over HTTPS GET and POST requests.
Application Layer Protocol:Web Protocols
Pupy can communicate over HTTP for C2.
Application Layer Protocol:Web Protocols
QakBot has the ability to use HTTP and HTTPS in communication with C2 servers.
Application Layer Protocol:Web Protocols
QUADAGENT uses HTTPS and HTTP for C2 communications.
Application Layer Protocol:Web Protocols
QUIETCANARY can use HTTPS for C2 communications.
Application Layer Protocol:Web Protocols
QuietSieve can use HTTPS in C2 communications.
Application Layer Protocol:Web Protocols
RainyDay can use HTTP in C2 communications.
Application Layer Protocol:Web Protocols
Ramsay has used HTTP for C2.
Application Layer Protocol:Web Protocols
It has used HTTP for C2.
Application Layer Protocol:Web Protocols
RATANKBA uses HTTP/HTTPS for command and control communication.
Application Layer Protocol:Web Protocols
RCSession can use HTTP in C2 communications.
Application Layer Protocol:Web Protocols
RDAT can use HTTP communications for C2, as well as using the WinHTTP library to make requests to the Exchange Web Services API.
Application Layer Protocol:Web Protocols
Some Reaver variants use HTTP for C2.
Application Layer Protocol:Web Protocols
RedLeaves can communicate to its C2 over HTTP and HTTPS if directed.
Application Layer Protocol:Web Protocols
The Regin malware platform supports many standard protocols, including HTTP and HTTPS.
Application Layer Protocol:Web Protocols
Remexi uses BITSAdmin to communicate with the C2 server over HTTP.
Application Layer Protocol:Web Protocols
Remsec is capable of using HTTP and HTTPS for C2.
Application Layer Protocol:Web Protocols
REvil has used HTTP and HTTPS in communication with C2.
Application Layer Protocol:Web Protocols
RGDoor uses HTTP for C2 communications.
Application Layer Protocol:Web Protocols
It has used RIPTIDE, a RAT that uses HTTP to communicate.
Application Layer Protocol:Web Protocols
Rising Sun has used HTTP and HTTPS for command and control.
Application Layer Protocol:Web Protocols
It has executed wget and curl commands to Pastebin over the HTTPS protocol.
Application Layer Protocol:Web Protocols
ROKRAT can use HTTP and HTTPS for command and control communication.
Application Layer Protocol:Web Protocols
It has initiated connections to external domains using HTTPS.
Application Layer Protocol:Web Protocols
S-Type uses HTTP for C2.
Application Layer Protocol:Web Protocols
Saint Bot has used HTTP for C2 communications.
Application Layer Protocol:Web Protocols
Sakula uses HTTP for C2.
Application Layer Protocol:Web Protocols
It's BCS-server tool connects to the designated C2 server via HTTP.
Application Layer Protocol:Web Protocols
SeaDuke uses HTTP and HTTPS for C2.
Application Layer Protocol:Web Protocols
Seasalt uses HTTP for C2 communications.
Application Layer Protocol:Web Protocols
ServHelper uses HTTP for C2.
Application Layer Protocol:Web Protocols
ShadowPad communicates over HTTP to retrieve a string that is decoded into a C2 server URL.
Application Layer Protocol:Web Protocols
Shamoon has used HTTP for C2.
Application Layer Protocol:Web Protocols
Shark has the ability to use HTTP in C2 communications.
Application Layer Protocol:Web Protocols
ShimRat communicated over HTTP and HTTPS with C2 servers.
Application Layer Protocol:Web Protocols
ShimRatReporter communicated over HTTP with preconfigured C2 servers.
Application Layer Protocol:Web Protocols
Sibot communicated with its C2 server via HTTP GET requests.
Application Layer Protocol:Web Protocols
SideTwist has used HTTP GET and POST requests over port 443 for C2.
Application Layer Protocol:Web Protocols
It has used HTTP in C2 communications.
Application Layer Protocol:Web Protocols
It uses HTTP for C2 communications.
Application Layer Protocol:Web Protocols
Sliver has the ability to support C2 communications over HTTP/S.
Application Layer Protocol:Web Protocols
SLOTHFULMEDIA has used HTTP and HTTPS for C2 communications.
Application Layer Protocol:Web Protocols
Small Sieve can contact actor-controlled C2 servers by using the Telegram API over HTTPS.
Application Layer Protocol:Web Protocols
Smoke Loader uses HTTP for C2.
Application Layer Protocol:Web Protocols
SMOKEDHAM has communicated with its C2 servers via HTTPS and HTTP POST requests.
Application Layer Protocol:Web Protocols
SNUGRIDE communicates with its C2 server over HTTP.
Application Layer Protocol:Web Protocols
During the SolarWinds Compromise, It used HTTP for C2 and data exfiltration.
Application Layer Protocol:Web Protocols
SoreFang can use HTTP in C2 communications.
Application Layer Protocol:Web Protocols
Spark has used HTTP POST requests to communicate with its C2 server to receive commands.
Application Layer Protocol:Web Protocols
SpeakUp uses POST and GET requests over HTTP to communicate with its main C&C server.
Application Layer Protocol:Web Protocols
Squirrelwaffle has used HTTP POST requests for C2 communications.
Application Layer Protocol:Web Protocols
STARWHALE has the ability to contact actor-controlled C2 servers via HTTP.
Application Layer Protocol:Web Protocols
It malware communicates with its C2 server via HTTPS.
Application Layer Protocol:Web Protocols
StrongPity can use HTTP and HTTPS in C2 communications.
Application Layer Protocol:Web Protocols
Stuxnet uses HTTP to communicate with a command and control server.
Application Layer Protocol:Web Protocols
A SUGARDUMP variant has used HTTP for C2.
Application Layer Protocol:Web Protocols
SUNBURST communicated via HTTP GET or HTTP POST requests to third party servers for C2.
Application Layer Protocol:Web Protocols
SUPERNOVA had to receive an HTTP GET request containing a specific set of parameters in order to execute.
Application Layer Protocol:Web Protocols
SVCReady can communicate with its C2 servers via HTTP.
Application Layer Protocol:Web Protocols
Sys10 uses HTTP for C2.
Application Layer Protocol:Web Protocols
It has used HTTP to communicate with C2 nodes.
Application Layer Protocol:Web Protocols
It has used HTTP for C2 communications.
Application Layer Protocol:Web Protocols
Taidoor has used HTTP GET and POST requests for C2.
Application Layer Protocol:Web Protocols
It has the curl command to send credentials over HTTP and the curl and wget commands to download new software. It has also used a custom user agent HTTP header in shell scripts.
Application Layer Protocol:Web Protocols
ThiefQuest uploads files via unencrypted HTTP.
Application Layer Protocol:Web Protocols
It malware has used HTTP for C2.
Application Layer Protocol:Web Protocols
TinyIt can use HTTPS in C2 communications.
Application Layer Protocol:Web Protocols
Tomiris can use HTTP to establish C2 communications.
Application Layer Protocol:Web Protocols
Torisma can use HTTP and HTTPS for C2 communications.
Application Layer Protocol:Web Protocols
TrailBlazer has used HTTP requests for C2.
Application Layer Protocol:Web Protocols
TrickBot uses HTTPS to communicate with its C2 servers, to get malware updates, modules that perform most of the malware logic and various configuration files.
Application Layer Protocol:Web Protocols
Trojan.Karagany can communicate with C2 via HTTP POST requests.
Application Layer Protocol:Web Protocols
It has used HTTP in communication with the C2.
Application Layer Protocol:Web Protocols
TSCookie can multiple protocols including HTTP and HTTPS in communication with command and control (C2) servers.
Application Layer Protocol:Web Protocols
Turian has the ability to use HTTP for its C2.
Application Layer Protocol:Web Protocols
It has used HTTP and HTTPS for C2 communications.
Application Layer Protocol:Web Protocols
UBoatRAT has used HTTP for C2 communications.
Application Layer Protocol:Web Protocols
UPPERCUT has used HTTP for C2, including sending error codes in Cookie headers.
Application Layer Protocol:Web Protocols
Uroburos can use a custom HTTP-based protocol for large data communications that can blend with normal network traffic by riding on top of standard HTTP.