prompt
stringclasses 508
values | procedure
stringlengths 20
478
|
|---|---|
Data Encoding:Standard Encoding
|
RogueRobin base64 encodes strings that are sent to the C2 over its DNS tunnel.
|
Data Encoding:Standard Encoding
|
RotaJakiro uses ZLIB Compression to compresses data sent to the C2 server in the payload section network communication packet.
|
Data Encoding:Standard Encoding
|
S-Type uses Base64 encoding for C2 traffic.
|
Data Encoding:Standard Encoding
|
Saint Bot has used Base64 to encode its C2 communications.
|
Data Encoding:Standard Encoding
|
It's BCS-server tool uses base64 encoding and HTML tags for the communication traffic between the C2 server.
|
Data Encoding:Standard Encoding
|
Sardonic can encode client ID data in 32 uppercase hex characters and transfer to the actor-controlled C2 server.
|
Data Encoding:Standard Encoding
|
SeaDuke C2 traffic is base64-encoded.
|
Data Encoding:Standard Encoding
|
SideTwist has used Base64 for encoded C2 traffic.
|
Data Encoding:Standard Encoding
|
Sliver can use standard encoding techniques like gzip and hex to ASCII to encode the C2 communication payload.
|
Data Encoding:Standard Encoding
|
SMOKEDHAM has encoded its C2 traffic with Base64.
|
Data Encoding:Standard Encoding
|
Spark has encoded communications with the C2 server with base64.
|
Data Encoding:Standard Encoding
|
SpeakUp encodes C&C communication using Base64.
|
Data Encoding:Standard Encoding
|
Squirrelwaffle has encoded its communications to C2 servers using Base64.
|
Data Encoding:Standard Encoding
|
STARWHALE has the ability to hex-encode collected data from an infected host.
|
Data Encoding:Standard Encoding
|
Stuxnet transforms encrypted binary data into an ASCII string in order to use it as a URL parameter value.
|
Data Encoding:Standard Encoding
|
SUNBURST used Base64 encoding in its C2 traffic.
|
Data Encoding:Standard Encoding
|
SysUpdate has used Base64 to encode its C2 traffic.
|
Data Encoding:Standard Encoding
|
It has used encoded ASCII text for initial C2 communications.
|
Data Encoding:Standard Encoding
|
Torisma has encoded C2 communications with Base64.
|
Data Encoding:Standard Encoding
|
TrickBot can Base64-encode C2 commands.
|
Data Encoding:Standard Encoding
|
It has used base64 encoding to hide command strings delivered from the C2.
|
Data Encoding:Standard Encoding
|
Valak has returned C2 data as encoded ASCII.
|
Data Encoding:Standard Encoding
|
WellMess has used Base64 encoding to uniquely identify communication to and from the C2.
|
Data Encoding:Standard Encoding
|
xCaon has used Base64 to encode its C2 traffic.
|
Data Encoding:Standard Encoding
|
Zebrocy has used URL/Percent Encoding on data exfiltrated via HTTP POST requests.
|
Data Encoding:Non-Standard Encoding
|
Newer variants of BACKSPACE will encode C2 communications with a custom system.
|
Data Encoding:Non-Standard Encoding
|
Bankshot encodes commands from the control server using a range of characters and gzip.
|
Data Encoding:Non-Standard Encoding
|
Cyclops Blink can use a custom binary scheme to encode messages with specific commands and parameters to be executed.
|
Data Encoding:Non-Standard Encoding
|
InvisiMole can use a modified base32 encoding to encode data within the subdomain of C2 requests.
|
Data Encoding:Non-Standard Encoding
|
NightClub has used a non-standard encoding in DNS tunneling removing any = from the result of base64 encoding, and replacing / characters with -s and + characters with -p.
|
Data Encoding:Non-Standard Encoding
|
OceanSalt can encode data with a NOT operation before sending the data to the control server.
|
Data Encoding:Non-Standard Encoding
|
PowGoop can use a modified Base64 encoding mechanism to send data to and from the C2 server.
|
Data Encoding:Non-Standard Encoding
|
RDAT can communicate with the C2 via subdomains that utilize base64 with character substitutions.
|
Data Encoding:Non-Standard Encoding
|
ShadowPad has encoded data as readable Latin characters.
|
Data Encoding:Non-Standard Encoding
|
Small Sieve can use a custom hex byte swapping encoding scheme to obfuscate tasking traffic.
|
Data Encoding:Non-Standard Encoding
|
Uroburos can use a custom base62 and a de-facto base32 encoding that uses digits 0-9 and lowercase letters a-z in C2 communications.
|
Data Obfuscation
|
FlawedAmmyy may obfuscate portions of the initial C2 handshake.
|
Data Obfuscation
|
FunnyDream can send compressed and obfuscated packets to C2.
|
Data Obfuscation
|
During Operation Wocao, threat actors encrypted IP addresses used for "Agent" proxy hops with RC4.
|
Data Obfuscation
|
RDAT has used encoded data within subdomains as AES ciphertext to communicate from the host to the C2.
|
Data Obfuscation
|
SideTwist can embed C2 responses in the source code of a fake Flickr webpage.
|
Data Obfuscation
|
SLOTHFULMEDIA has hashed a string containing system information prior to exfiltration via POST requests.
|
Data Obfuscation
|
TrailBlazer can masquerade its C2 traffic as legitimate Google Notifications HTTP requests.
|
Data Obfuscation:Junk Data
|
It added "junk data" to each encoded string, preventing trivial decoding without knowledge of the junk removal algorithm. Each implant was given a "junk length" value when created, tracked by the controller software to allow seamless communication but prevent analysis of the command protocol on the wire.
|
Data Obfuscation:Junk Data
|
BendyBear has used byte randomization to obscure its behavior.
|
Data Obfuscation:Junk Data
|
Downdelph inserts pseudo-random characters between each original character during encoding of C2 network requests, making it difficult to write signatures on them.
|
Data Obfuscation:Junk Data
|
GoldMax has used decoy traffic to surround its malicious network traffic to avoid detection.
|
Data Obfuscation:Junk Data
|
GrimAgent can pad C2 messages with random generated values.
|
Data Obfuscation:Junk Data
|
Kevin can generate a sequence of dummy HTTP C2 requests to obscure traffic.
|
Data Obfuscation:Junk Data
|
Mori has obfuscated the FML.dll with 200MB of junk data.
|
Data Obfuscation:Junk Data
|
P2P ZeuS added junk data to outgoing UDP packets to peer implants.
|
Data Obfuscation:Junk Data
|
P8RAT can send randomly-generated data as part of its C2 communication.
|
Data Obfuscation:Junk Data
|
PLEAD samples were found to be highly obfuscated with junk code.
|
Data Obfuscation:Junk Data
|
SUNBURST added junk bytes to its C2 over HTTP.
|
Data Obfuscation:Junk Data
|
TrailBlazer has used random identifier strings to obscure its C2 operations and result codes.
|
Data Obfuscation:Junk Data
|
Turian can insert pseudo-random characters into its network encryption setup.
|
Data Obfuscation:Junk Data
|
Uroburos can add extra characters in encoded strings to help mimic DNS legitimate requests.
|
Data Obfuscation:Junk Data
|
WellMess can use junk data in the Base64 string for additional obfuscation.
|
Data Obfuscation:Steganography
|
It has used steganography to hide its C2 communications.
|
Data Obfuscation:Steganography
|
Daserf can use steganography to hide malicious code downloaded to the victim.
|
Data Obfuscation:Steganography
|
When the Duqu command and control is operating over HTTP or HTTPS, Duqu uploads data to its controller by appending it to a blank JPG file.
|
Data Obfuscation:Steganography
|
HAMMERTOSS is controlled via commands that are appended to image files.
|
Data Obfuscation:Steganography
|
LightNeuron is controlled via commands that are embedded into PDFs and JPGs using steganographic methods.
|
Data Obfuscation:Steganography
|
During Operation Ghost, It used steganography to hide the communications between the implants and their C&C servers.
|
Data Obfuscation:Steganography
|
RDAT can process steganographic images attached to email messages to send and receive C2 commands. RDAT can also embed additional messages within BMP images to communicate with the RDAT operator.
|
Data Obfuscation:Steganography
|
Sliver can encode binary data into a .PNG file for C2 communication.
|
Data Obfuscation:Steganography
|
SUNBURST C2 data attempted to appear as benign XML related to .NET assemblies or as a faux JSON blob.
|
Data Obfuscation:Steganography
|
ZeroT has retrieved stage 2 payloads as Bitmap images that use Least Significant Bit (LSB) steganography.
|
Data Obfuscation:Steganography
|
Zox has used the .PNG file format for C2 communications.
|
Data Obfuscation:Protocol Impersonation
|
BADCALL uses a FakeTLS method during C2.
|
Data Obfuscation:Protocol Impersonation
|
Bankshot generates a false TLS handshake using a public certificate to disguise C2 network communications.
|
Data Obfuscation:Protocol Impersonation
|
During C0017, It frequently configured the URL endpoints of their stealthy passive backdoor LOWKEY.PASSIVE to masquerade as normal web application traffic on an infected server.
|
Data Obfuscation:Protocol Impersonation
|
Cobalt Strike can mimic the HTTP protocol for C2 communication, while hiding the actual data in either an HTTP header, URI parameter, the transaction body, or appending it to the URI.
|
Data Obfuscation:Protocol Impersonation
|
FakeM C2 traffic attempts to evade detection by resembling data generated by legitimate messenger applications, such as MSN and Yahoo! messengers. Additionally, some variants of FakeM use modified SSL code for communications back to C2 servers, making SSL decryption ineffective.
|
Data Obfuscation:Protocol Impersonation
|
FALLCHILL uses fake Transport Layer Security (TLS) to communicate with its C2 server.
|
Data Obfuscation:Protocol Impersonation
|
HARDRAIN uses FakeTLS to communicate with its C2 server.
|
Data Obfuscation:Protocol Impersonation
|
It used a FakeTLS session for C2 communications.
|
Data Obfuscation:Protocol Impersonation
|
InvisiMole can mimic HTTP protocol with custom HTTP "verbs" HIDE, ZVVP, and NOP.
|
Data Obfuscation:Protocol Impersonation
|
KeyBoy uses custom SSL libraries to impersonate SSL in C2 traffic.
|
Data Obfuscation:Protocol Impersonation
|
It malware also uses a unique form of communication encryption known as FakeTLS that mimics TLS but uses a different encryption method, potentially evading SSL traffic inspection/decryption.
|
Data Obfuscation:Protocol Impersonation
|
Okrum mimics HTTP protocol for C2 communication, while hiding the actual messages in the Cookie and Set-Cookie headers of the HTTP requests.
|
Data Obfuscation:Protocol Impersonation
|
SUNBURST masqueraded its network traffic as the Orion Improvement Program (OIP) protocol.
|
Data Obfuscation:Protocol Impersonation
|
TAINTEDSCRIBE has used FakeTLS for session authentication.
|
Data Obfuscation:Protocol Impersonation
|
Uroburos can use custom communication methodologies that ride over common protocols including TCP, UDP, HTTP, SMTP, and DNS in order to blend with normal network traffic.
|
Dynamic Resolution
|
It has used Dynamic DNS providers for their malware C2 infrastructure.
|
Dynamic Resolution
|
AsyncRAT can be configured to use dynamic DNS.
|
Dynamic Resolution
|
Bisonal has used a dynamic DNS service for C2.
|
Dynamic Resolution
|
It has used DDNS for C2 communications.
|
Dynamic Resolution
|
During C0026, the threat actors re-registered a ClouDNS dynamic DNS subdomain which was previously used by ANDROMEDA.
|
Dynamic Resolution
|
It has incorporated dynamic DNS domains in its infrastructure.
|
Dynamic Resolution
|
Gelsemium can use dynamic DNS domain names in C2.
|
Dynamic Resolution
|
Maze has forged POST strings with a random choice from a list of possibilities including "forum", "php", "view", etc. while making connection with the C2, hindering detection efforts.
|
Dynamic Resolution
|
NETEAGLE can use HTTP to download resources that contain an IP address and port number pair to connect to for C2.
|
Dynamic Resolution
|
During Night Dragon, threat actors used dynamic DNS services for C2.
|
Dynamic Resolution
|
For Operation Dust Storm, the threat actors used dynamic DNS domains from a variety of free providers, including No-IP, Oray, and 3322.
|
Dynamic Resolution
|
For Operation Spalax, the threat actors used dynamic DNS services, including Duck DNS and DNS Exit, as part of their C2 infrastructure.
|
Dynamic Resolution
|
It has resolved Pony C2 server IP addresses by either converting Bitcoin blockchain transaction data to specific octets, or accessing IP addresses directly within the Namecoin blockchain.
|
Dynamic Resolution
|
During the SolarWinds Compromise, It used dynamic DNS resolution to construct and resolve to randomly-generated subdomains for C2.
|
Dynamic Resolution
|
SUNBURST dynamically resolved C2 infrastructure for randomly-generated subdomains within a parent domain.
|
Dynamic Resolution
|
It has used dynamic DNS services for C2 infrastructure.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.