MITRE ATT&CK T1559.002: Dynamic Data Exchange
When to use this skill
Use this skill when the task involves T1559.002, Dynamic Data Exchange, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1559.002
- Technique name: Dynamic Data Exchange
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1559/002
- Tactics: execution
- Platforms: Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may use Windows Dynamic Data Exchange (DDE) to execute arbitrary commands. DDE is a client-server protocol for one-time and/or continuous inter-process communication (IPC) between applications. Once a link is established, applications can autonomously exchange transactions consisting of strings, warm data links (notifications when a data item changes), hot data links (duplications of changes to a data item), and requests for command execution.
Object Linking and Embedding (OLE), or the ability to link data between documents, was originally implemented through DDE. Despite being superseded by Component Object Model, DDE may be enabled in Windows 10 and most of Microsoft Office 2016 via Registry keys.(Citation: BleepingComputer DDE Disabled in Word Dec 2017)(Citation: Microsoft ADV170021 Dec 2017)(Citation: Microsoft DDE Advisory Nov 2017)
Microsoft Office documents can be poisoned with DDE commands, directly or through embedded files, and used to deliver execution via Phishing campaigns or hosted Web content, avoiding the use of Visual Basic for Applications (VBA) macros.(Citation: SensePost PS DDE May 2016)(Citation: Kettle CSV DDE Aug 2014)(Citation: Enigma Reviving DDE Jan 2018)(Citation: SensePost MacroLess DDE Oct 2017) Similarly, adversaries may infect payloads to execute applications and/or commands on a victim device by way of embedding DDE formulas within a CSV file intended to be opened through a Windows spreadsheet program.(Citation: OWASP CSV Injection)(Citation: CSV Excel Macro Injection )
DDE could also be leveraged by an adversary operating on a compromised machine who does not have direct access to a Command and Scripting Interpreter. DDE execution can be invoked remotely via Remote Services such as Distributed Component Object Model (DCOM).(Citation: Fireeye Hunting COM June 2019)
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Application Isolation and Sandboxing
- Behavior Prevention on Endpoint
- Disable or Remove Feature or Program
- Software Configuration
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT28 (intrusion-set)
- APT37 (intrusion-set)
- BITTER (intrusion-set)
- Cobalt Group (intrusion-set)
- FIN7 (intrusion-set)
- Gallmaker (intrusion-set)
- GravityRAT (malware)
- HAWKBALL (malware)
- KeyBoy (malware)
- Leviathan (intrusion-set)
- MuddyWater (intrusion-set)
- Operation Sharpshooter (campaign)
- POWERSTATS (malware)
- Patchwork (intrusion-set)
- PoetRAT (malware)
- RTM (malware)
- Ramsay (malware)
- Sidewinder (intrusion-set)
- TA505 (intrusion-set)
- Valak (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ent-t1559-002-dynamic-data-exchange3description: "Analyze MITRE ATT&CK T1559.002 Dynamic Data Exchange in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1559.002, Dynamic Data Exchange, or enterprise ATT&CK. Adversaries may use Windows Dynamic Data Exchange (DDE) to execute arbitrary commands."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1559-002-dynamic-data-exchange7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1559.00210 attack_stix_id: attack-pattern--232a7e42-cd6e-4902-8fe9-2960f529dd4d11 attack_version: "1.4"12 attack_modified: "2025-10-24T17:48:31.581Z"13---1415# MITRE ATT&CK T1559.002: Dynamic Data Exchange1617## When to use this skill1819Use this skill when the task involves T1559.002, Dynamic Data Exchange, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1559.00225- Technique name: Dynamic Data Exchange26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1559/00228- Tactics: execution29- Platforms: Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may use Windows Dynamic Data Exchange (DDE) to execute arbitrary commands. DDE is a client-server protocol for one-time and/or continuous inter-process communication (IPC) between applications. Once a link is established, applications can autonomously exchange transactions consisting of strings, warm data links (notifications when a data item changes), hot data links (duplications of changes to a data item), and requests for command execution.3738Object Linking and Embedding (OLE), or the ability to link data between documents, was originally implemented through DDE. Despite being superseded by [Component Object Model](https://attack.mitre.org/techniques/T1559/001), DDE may be enabled in Windows 10 and most of Microsoft Office 2016 via Registry keys.(Citation: BleepingComputer DDE Disabled in Word Dec 2017)(Citation: Microsoft ADV170021 Dec 2017)(Citation: Microsoft DDE Advisory Nov 2017)3940Microsoft Office documents can be poisoned with DDE commands, directly or through embedded files, and used to deliver execution via [Phishing](https://attack.mitre.org/techniques/T1566) campaigns or hosted Web content, avoiding the use of Visual Basic for Applications (VBA) macros.(Citation: SensePost PS DDE May 2016)(Citation: Kettle CSV DDE Aug 2014)(Citation: Enigma Reviving DDE Jan 2018)(Citation: SensePost MacroLess DDE Oct 2017) Similarly, adversaries may infect payloads to execute applications and/or commands on a victim device by way of embedding DDE formulas within a CSV file intended to be opened through a Windows spreadsheet program.(Citation: OWASP CSV Injection)(Citation: CSV Excel Macro Injection )4142DDE could also be leveraged by an adversary operating on a compromised machine who does not have direct access to a [Command and Scripting Interpreter](https://attack.mitre.org/techniques/T1059). DDE execution can be invoked remotely via [Remote Services](https://attack.mitre.org/techniques/T1021) such as [Distributed Component Object Model](https://attack.mitre.org/techniques/T1021/003) (DCOM).(Citation: Fireeye Hunting COM June 2019)4344## Agent workflow45461. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.472. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.483. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.494. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.505. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.516. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5253## Bundled resources5455- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.56- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.57- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.58- `templates/detection-brief.md`: detection engineering brief template.59- `templates/hunt-plan.md`: threat hunt plan template.60- `templates/incident-response-note.md`: incident response note template.61- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.62- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.63- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6465To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6667## Detection guidance6869No ATT&CK detection guidance was present in the source STIX object.7071## Useful telemetry and data sources7273- Not specified in the STIX object.7475## Mitigations to consider7677- Application Isolation and Sandboxing78- Behavior Prevention on Endpoint79- Disable or Remove Feature or Program80- Software Configuration8182## Known threat context8384Use these examples only as contextual leads, not as proof that an observed event is this technique:8586- APT28 (intrusion-set)87- APT37 (intrusion-set)88- BITTER (intrusion-set)89- Cobalt Group (intrusion-set)90- FIN7 (intrusion-set)91- Gallmaker (intrusion-set)92- GravityRAT (malware)93- HAWKBALL (malware)94- KeyBoy (malware)95- Leviathan (intrusion-set)96- MuddyWater (intrusion-set)97- Operation Sharpshooter (campaign)98- POWERSTATS (malware)99- Patchwork (intrusion-set)100- PoetRAT (malware)101- RTM (malware)102- Ramsay (malware)103- Sidewinder (intrusion-set)104- TA505 (intrusion-set)105- Valak (malware)106107## Recommended output pattern108109When responding with this skill, structure the answer as:110111- Assessment: whether the evidence supports this ATT&CK mapping and why.112- Evidence: specific indicators, logs, behaviors, and assumptions.113- Detection: telemetry sources, analytic logic, and tuning considerations.114- Response: containment, eradication, recovery, and validation actions.115- Coverage gaps: missing logs, sensors, controls, or environmental details.116- References: include the ATT&CK URL and any user-provided evidence references.