Live Active security incident? Get immediate response
MITRE ATT&CK® Technique

T1001.002: Steganography

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.

EnterpriseT1001.002Sub-techniqueObject v1.1 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

Steganography matters because it can make command-and-control traffic look like ordinary digital content, such as image or document files, rather than obvious malware traffic. For leaders, the practical issue is whether the organization can correlate file movement with network behavior well enough to spot hidden C2 across Windows, Linux, macOS, and ESXi environments.

Executive priority

Treat this as a control-validation problem for C2 resilience, not just a malware-analysis topic. Ask whether network boundary inspection, file telemetry, and SOC correlation are strong enough to investigate suspicious file-based communications, especially on servers and platforms where logging may be weaker. The ATT&CK relationships show use across multiple malware families and a campaign/group context, but they do not by themselves indicate current exposure or attribution to any environment.

Technical view

This is a command-and-control sub-technique under Data Obfuscation. Because ATT&CK provides no official detection text, SOC teams should map coverage to the related detection strategy DET0235: correlating files with network activity. Validate visibility for inbound and outbound transfers of image/document-like content, network boundary alerts, and unusual C2-like patterns across Linux, macOS, Windows, and ESXi. Relationship context includes Windows-heavy software examples, plus Linux/macOS coverage in some related software, so do not limit validation to a single endpoint platform.

Likely telemetry

  • Network session and flow records for outbound and inbound communications
  • Proxy, web gateway, firewall, IDS, and IPS logs at network boundaries
  • File transfer metadata and retained samples where legally and operationally permitted
  • Endpoint or server file creation/modification telemetry for received or staged image/document-like files
  • Email or messaging telemetry where file-based communications are in scope

Detection direction

  • Use file-plus-network correlation rather than relying only on content inspection; steganography is specifically intended to make C2 harder to recognize.
  • Tune for suspicious combinations: repeated file transfers, unusual destinations, boundary alerts, and file activity on systems that do not normally exchange such content.
  • Account for false positives from legitimate image, document, marketing, engineering, and user-generated content workflows.
  • Validate ATT&CK mapping against DET0235 if that strategy is implemented locally; ATT&CK does not provide native detection logic for this sub-technique.
  • Review blind spots on non-user endpoints, servers, and ESXi environments, where file and network telemetry may be less complete.

Mitigation priorities

  • Prioritize M1031 Network Intrusion Prevention at network boundaries using intrusion detection signatures to block or alert on relevant traffic.
  • Ensure boundary controls produce evidence the SOC can correlate with file activity and incident timelines.
  • Sequence control validation from highest-risk egress points and server networks before expanding to lower-risk segments.
  • Do not depend on a single signature or content rule; use layered network prevention, logging, and investigation workflows.
Analyst notes and limits

The relationship set ties this behavior to Data Obfuscation, Operation Ghost, Axiom, and multiple software entries including HAMMERTOSS, Duqu, Daserf, ZeroT, LightNeuron, RDAT, SUNBURST, Sliver, Zox, LunarWeb, and LunarMail. Use these as ATT&CK context for threat modeling and detection prioritization, not as proof of activity in a specific environment.

Official ATT&CK detection guidance is not provided for this object. The recommendations above are limited to the supplied description, platforms, tactic, DET0235 detection-strategy relationship, M1031 mitigation relationship, and listed use relationships. Local telemetry, file-retention policy, legal constraints, and normal business file-transfer patterns are required to assess actual coverage.

Official MITRE ATT&CK definition

Steganography

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.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Related techniques

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

1 rows
Domain ID Name Relationship / procedure
Enterprise T1001 Data Obfuscation This object subtechnique of Data Obfuscation.
Associated objects

Groups, software, and campaigns

Group Enterprise

G0001: Axiom

Axiom is a suspected Chinese cyber espionage group that has targeted the aerospace, defense, government, manufacturing, and media sectors since at least 2008. Some reporting suggests a degree of overlap between Axiom and Winnti Group but the two groups appear to be distinct based on differences in reporting on TTPs and targeting.[1][2][3]

Tool Enterprise

S0633: Sliver

Sliver is an open source, cross-platform, red team command and control (C2) framework written in Golang. Sliver includes its own package manager, "armory," for staging and downloading additional tools and payloads to the primary C2 framework.[1][2]

WindowsLinuxmacOS
Malware Enterprise

S0395: LightNeuron

LightNeuron is a sophisticated backdoor that has targeted Microsoft Exchange servers since at least 2014. LightNeuron has been used by Turla to target diplomatic and foreign affairs-related organizations. The presence of certain strings in the malware suggests a Linux variant of LightNeuron exists.[1]

WindowsLinux
Malware Enterprise

S0187: Daserf

Daserf is a backdoor that has been used to spy on and steal from Japanese, South Korean, Russian, Singaporean, and Chinese victims. Researchers have identified versions written in both Visual C and Delphi. [1] [2]

Windows
Malware Enterprise

S0495: RDAT

RDAT is a backdoor used by the suspected Iranian threat group OilRig. RDAT was originally identified in 2017 and targeted companies in the telecommunications sector.[1]

Windows
Malware Enterprise

S0038: Duqu

Duqu is a malware platform that uses a modular approach to extend functionality after deployment within a target network. [1]

Windows
Campaign Enterprise

C0023: Operation Ghost

Operation Ghost was an APT29 campaign starting in 2013 that included operations against ministries of foreign affairs in Europe and the Washington, D.C. embassy of a European Union country. During Operation Ghost, APT29 used new families of malware and leveraged web services, steganography, and unique C2 infrastructure for each victim.[1]

Relationship explorer

All related ATT&CK context

Mitigations

Mitigation direction

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .

ATT&CK release
19.1
Object version
1.1
Created
Modified
Raw hash
217e0ed990d08c6d...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.1 Current bundle 217e0ed990d0…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    University of Birmingham C2

    Gardiner, J., Cova, M., Nagaraja, S. (2014, February). Command & Control Understanding, Denying and Detecting. Retrieved April 20, 2016.

    Open source URL
  2. [2]
    mitre-attack T1001.002
    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.