Technique:  Data Encoding:Standard Encoding
C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding.
An It HTTP malware variant used Base64 to encode communications to the C2 server.
It has used base64 to encode command and control traffic.
Astaroth encodes data using Base64 before sending it to the C2 server.
AutoIt backdoor has sent a C2 response that was base64-encoded.
BabyShark has encoded data using certutil before exfiltration.
Some Backdoor.Oldrea samples use standard Base64 + bzip2, and some use standard Base64 + reverse XOR + RSA-2048 to decrypt data received from C2 servers.
BADNEWS encodes C2 traffic with base64.
Bisonal has encoded binary data with Base64 and ASCII.
BLINDINGCAN has encoded its C2 traffic with Base64.
Several It tools encode data with base64 when posting it to a C2 server.
BS2005 uses Base64 encoding for communication in the message body of an HTTP request.
Bumblebee has the ability to base64 encode C2 server responses.
It encodes the message body of HTTP traffic with Base64.
Chaes has used Base64 to encode C2 communications.
CharmPower can send additional modules over C2 encoded with base64.
ChChes can encode C2 data with a custom technique that utilizes Base64.
Cobalt Strike can use Base64, URL-safe Base64, or NetBIOS encoding in its C2 traffic.
Cobian RAT obfuscates communications with the C2 server using Base64 encoding.
CORESHELL C2 messages are Base64-encoded.
CreepySnail can use Base64 to encode its C2 traffic.
DarkWatchman encodes data using hexadecimal representation before sending it to the C2 server.
Daserf uses custom base64 encoding to obfuscate HTTP traffic.
Denis encodes the data sent to the server in Base64.
Dipsind encodes C2 traffic with base64.
DnsSystem can Base64 encode data sent to C2.
down_new has the ability to base64 encode C2 communications.
Ebury has encoded C2 traffic in hexadecimal format.
Elise exfiltrates data using cookie values that are Base64-encoded.
Emotet has used Google’s Protobufs to serialize data sent to and from the C2 server.
Some Felismus samples use a custom method for C2 traffic that utilizes Base64.
Flagpro has encoded bidirectional data communications between a target system and C2 server using Base64.
Fysbis can use Base64 to encode its C2 traffic.
gh0st RAT has used Zlib to compress C2 communications data before encrypting it.
GrimAgent can base64 encode C2 replies.
It has used ASCII encoding for C2 traffic.
For C2 over HTTP, Helminth encodes data with base64 and sends it via the "Cookie" field of HTTP requests. For C2 over DNS, Helminth converts ASCII characters into their hexadecimal values and sends the data in cleartext.
HOPLIGHT has utilized Zlib compression to obfuscate the communications payload.
Ixeshe uses custom Base64 encoding schemes to obfuscate command and control traffic in the message body of HTTP requests.
A JHUHUGIT variant encodes C2 POST data base64.
Kazuar encodes communications to the C2 server in Base64.
Kessel has exfiltrated data via hexadecimal-encoded subdomain fields of DNS queries.
Kevin can Base32 encode chunks of output files during exfiltration.
KONNI has used a custom base64 key to encode stolen data before exfiltration.
A It malware sample encodes data with base64.
It has used base64 encoding.
Mafalda can encode data using Base64 prior to exfiltration.
MechaFlounder has the ability to use base16 encoded strings in C2.
Mis-Type uses Base64 encoding for C2 traffic.
Misdat network traffic is Base64-encoded plaintext.
Mongall can use Base64 to encode information sent to its C2.
More_eggs has used basE91 encoding, along with encryption, for C2 communication.
Mori can use Base64 encoded JSON libraries used in C2.
It has used tools to encode C2 communications including Base64 encoding.
njRAT uses Base64 encoding for C2 traffic.
Octopus has encoded C2 communications in Base64.
Okrum has used base64 to encode C2 communication.
OopsIE encodes data in hexadecimal format over the C2 channel.
OSX_OCEANLOTUS.D has used zlib to compress all data after 0x52 for the custom TCP C2 protocol.
It used Base64 to encode C2 traffic.
PingPull can encode C2 traffic with Base64.
Responses from the Pisloader C2 server are base32-encoded.
PowerShower has the ability to encode C2 communications with base64 encoding.
POWERSTATS encoded C2 traffic with base64.
POWRUNER can use base64 encoded C2 communications.
Prikormka encodes C2 traffic with Base64.
QakBot can Base64 encode system information sent to C2.
QUADAGENT encodes C2 communications with base64.
QUIETCANARY can base64 encode C2 communications.
Ramsay has used base64 to encode its C2 traffic.
RDAT can communicate with the C2 via base32-encoded subdomains.
Revenge RAT uses Base64 to encode information sent to the C2 server.
RogueRobin base64 encodes strings that are sent to the C2 over its DNS tunnel.
RotaJakiro uses ZLIB Compression to compresses data sent to the C2 server in the payload section network communication packet.
S-Type uses Base64 encoding for C2 traffic.
Saint Bot has used Base64 to encode its C2 communications.
It's BCS-server tool uses base64 encoding and HTML tags for the communication traffic between the C2 server.
Sardonic can encode client ID data in 32 uppercase hex characters and transfer to the actor-controlled C2 server.
SeaDuke C2 traffic is base64-encoded.
SideTwist has used Base64 for encoded C2 traffic.
Sliver can use standard encoding techniques like gzip and hex to ASCII to encode the C2 communication payload.
SMOKEDHAM has encoded its C2 traffic with Base64.
Spark has encoded communications with the C2 server with base64.
SpeakUp encodes C&C communication using Base64.
Squirrelwaffle has encoded its communications to C2 servers using Base64.
STARWHALE has the ability to hex-encode collected data from an infected host.
Stuxnet transforms encrypted binary data into an ASCII string in order to use it as a URL parameter value.
SUNBURST used Base64 encoding in its C2 traffic.
SysUpdate has used Base64 to encode its C2 traffic.
It has used encoded ASCII text for initial C2 communications.
Torisma has encoded C2 communications with Base64.
TrickBot can Base64-encode C2 commands.
It has used base64 encoding to hide command strings delivered from the C2.
Valak has returned C2 data as encoded ASCII.
WellMess has used Base64 encoding to uniquely identify communication to and from the C2.
xCaon has used Base64 to encode its C2 traffic.
Zebrocy has used URL/Percent Encoding on data exfiltrated via HTTP POST requests.