Has used steganography to hide its C2 communications.1
- Tactic
- Command and Control
- Platforms
- Linux, macOS, Windows, ESXi
- Version
- 1.1
- Created
- 15 March 2020
- Last modified
- 24 October 2025
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult. Steganographic techniques can be used to hide data in digital messages that are transferred between systems. This hidden information can be used for command and control of compromised systems. In some cases, the passing of files embedded using steganography, such as image or document files, can be used for command and control.
Steganography MITRE reference T1001.002
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 1 groups for this technique
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During Operation Ghost, APT29 used steganography to hide the communications between the implants and their C&C servers.1
All 1 campaigns for this technique
11 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can parse IDAT chunks from .png files to look for zlib-compressed and AES encrypted C2 commands.1
Can receive C2 commands hidden in the structure of .jpg and .gif images.1
Has used the .PNG file format for C2 communications.1
Can encode binary data into a .PNG file for C2 communication.1
C2 data attempted to appear as benign XML related to .NET assemblies or as a faux JSON blob.123
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.1
All 11 software entries for this technique · 6 newest in this preview
Offense vs defense T1001.002
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Steganography detection strategy DET0235
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detecting Steganographic Command and Control via File + Network Correlation
AN0651 · Windows
Detect the creation or modification of common media file formats (e.g., .jpg, .png, .wav) following suspicious process activity like compression or encryption, especially when paired with lateral movement or exfiltration behavior.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
| Network Traffic ContentDC0085 | NSM:Flow | Session Transfer Content |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| FileExtensionFilter | Allows tuning of monitored file types (e.g., .jpg, .png, .docx). |
| PayloadEntropyThreshold | Threshold for flagging potential hidden data in outbound payloads. |
| ExecutionToExfilTimeWindow | Time window between media creation and network transmission. |
AN0652 · Linux
Unusual use of steganographic or media processing binaries (e.g., steghide, ffmpeg, imagemagick) followed by outbound communication to external IPs with high data output and media MIME types.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| File MetadataDC0059 | NSM:Flow | Observed File Transfers |
| Network Traffic ContentDC0085 | NSM:Flow | Captured File Content |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ToolNameMatch | Specify which binaries to monitor (e.g., steghide, outguess). |
| OutboundTrafficPattern | Adjust based on known normal file upload services. |
AN0653 · macOS
Abnormal usage of Preview, ImageMagick, or binary editors to alter images/documents, followed by exfiltration or outbound connections with mismatched file MIME types or payload structure.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | macos:osquery | process_events |
| File CreationDC0039 | macos:unifiedlog | File creation |
| Network Traffic ContentDC0085 | NSM:Flow | C2 exfiltration |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ParentProcessBaseline | Allow tuning based on expected apps calling image-editing tools. |
| TimeDelta | Gap between file manipulation and outbound connection. |
AN0654 · ESXi
Suspicious modification of file artifacts (e.g., logs, ISO templates) on ESXi datastores, followed by beaconing or POST operations to external IPs potentially hiding payloads in file-like traffic.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| File MetadataDC0059 | esxi:vmkernel | Storage access and file ops |
| Network Connection CreationDC0082 | esxi:hostd | Service initiated connections |
| Network Traffic ContentDC0085 | NSM:Flow | Transferred file observations |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| FilenamePattern | Tune for likely stego file names (e.g., wallpaper.jpg, template.iso). |
| UnusualDestinationIP | Destination outside vCenter management subnet. |
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate some obfuscation activity at the network level.
Tests from Atomic Red Team (MIT licence) · technique definition