Data Encoding

From enterprise
Jump to: navigation, search
Data Encoding
ID T1132
Tactic Command and Control
Platform Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows XP, Windows 7, Windows 8, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, Windows Vista, Windows 8.1, Linux, Windows 10, MacOS, OS X
Permissions Required User
Data Sources Packet capture, Process use of network, Process Monitoring, Network protocol analysis
Requires Network Yes
Contributors Itzik Kotler, SafeBreach

Command and control (C2) information is encoded using a standard data encoding system. Use of data encoding may be to adhere to existing protocol specifications and includes use of ASCII, Unicode, Base64, MIME, UTF-8, or other binary-to-text and character encoding systems.12 Some data encoding systems may also result in data compression, such as gzip.


  • Patchwork used Base64 to encode C2 traffic.3
  • C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding.4
  • AutoIt has sent a C2 response that was base64-encoded.5
  • BADNEWS encodes C2 traffic with base64.5
  • BS2005 uses Base64 encoding for communication in the message body of an HTTP request.6
  • CORESHELL C2 messages are Base64-encoded.7
  • Elise exfiltrates data using cookie values that are Base64-encoded.8
  • Mis-Type uses Base64 encoding for C2 traffic.9
  • Misdat network traffic is Base64-encoded plaintext.9
  • Responses from the Pisloader C2 server are base32-encoded.10
  • Prikormka encodes C2 traffic with Base64.11
  • S-Type uses Base64 encoding for C2 traffic.9
  • SeaDuke C2 traffic is base64-encoded.12


Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate activity at the network level. Signatures are often for unique indicators within protocols and may be based on the specific obfuscation technique used by a particular adversary or tool, and will likely be different across various malware families and versions. Adversaries will likely change tool C2 signatures over time or construct protocols in such a way as to avoid detection by common defensive tools.13


Analyze network data for uncommon data flows (e.g., a client sending significantly more data than it receives from a server). Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. Analyze packet contents to detect communications that do not follow the expected protocol behavior for the port that is being used.13