MITRE ATT&CK T1559.001: Component Object Model
When to use this skill
Use this skill when the task involves T1559.001, Component Object Model, 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.001
- Technique name: Component Object Model
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1559/001
- Tactics: execution
- Platforms: Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may use the Windows Component Object Model (COM) for local code execution. COM is an inter-process communication (IPC) component of the native Windows application programming interface (API) that enables interaction between software objects, or executable code that implements one or more interfaces.(Citation: Fireeye Hunting COM June 2019) Through COM, a client object can call methods of server objects, which are typically binary Dynamic Link Libraries (DLL) or executables (EXE).(Citation: Microsoft COM) Remote COM execution is facilitated by Remote Services such as Distributed Component Object Model (DCOM).(Citation: Fireeye Hunting COM June 2019)
Various COM interfaces are exposed that can be abused to invoke arbitrary execution via a variety of programming languages such as C, C++, Java, and Visual Basic.(Citation: Microsoft COM) Specific COM objects also exist to directly perform functions beyond code execution, such as creating a Scheduled Task/Job, fileless download/execution, and other adversary behaviors related to privilege escalation and persistence.(Citation: Fireeye Hunting COM June 2019)(Citation: ProjectZero File Write EoP Apr 2018)
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
- Privileged Account Management
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Bumblebee (malware)
- CLAIMLOADER (malware)
- DarkTortilla (malware)
- FunnyDream (malware)
- Gamaredon Group (intrusion-set)
- Gelsemium (malware)
- HermeticWizard (malware)
- InvisiMole (malware)
- Kimsuky (intrusion-set)
- Latrodectus (malware)
- Medusa Group (intrusion-set)
- Milan (malware)
- MuddyWater (intrusion-set)
- Neoichor (malware)
- POWERSTATS (malware)
- Ramsay (malware)
- Raspberry Robin (malware)
- RustyWater (malware)
- SILENTTRINITY (tool)
- STATICPLUGIN (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-001-component-object-model3description: "Analyze MITRE ATT&CK T1559.001 Component Object Model 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.001, Component Object Model, or enterprise ATT&CK. Adversaries may use the Windows Component Object Model (COM) for local code execution."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-001-component-object-model7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1559.00110 attack_stix_id: attack-pattern--2f6b4ed7-fef1-44ba-bcb8-1b4beb610b6411 attack_version: "1.2"12 attack_modified: "2025-10-24T17:48:35.814Z"13---1415# MITRE ATT&CK T1559.001: Component Object Model1617## When to use this skill1819Use this skill when the task involves T1559.001, Component Object Model, 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.00125- Technique name: Component Object Model26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1559/00128- Tactics: execution29- Platforms: Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may use the Windows Component Object Model (COM) for local code execution. COM is an inter-process communication (IPC) component of the native Windows application programming interface (API) that enables interaction between software objects, or executable code that implements one or more interfaces.(Citation: Fireeye Hunting COM June 2019) Through COM, a client object can call methods of server objects, which are typically binary Dynamic Link Libraries (DLL) or executables (EXE).(Citation: Microsoft COM) Remote COM execution is facilitated by [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)3738Various COM interfaces are exposed that can be abused to invoke arbitrary execution via a variety of programming languages such as C, C++, Java, and [Visual Basic](https://attack.mitre.org/techniques/T1059/005).(Citation: Microsoft COM) Specific COM objects also exist to directly perform functions beyond code execution, such as creating a [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053), fileless download/execution, and other adversary behaviors related to privilege escalation and persistence.(Citation: Fireeye Hunting COM June 2019)(Citation: ProjectZero File Write EoP Apr 2018)3940## Agent workflow41421. 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.432. 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.443. 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.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. 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.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- Application Isolation and Sandboxing74- Privileged Account Management7576## Known threat context7778Use these examples only as contextual leads, not as proof that an observed event is this technique:7980- Bumblebee (malware)81- CLAIMLOADER (malware)82- DarkTortilla (malware)83- FunnyDream (malware)84- Gamaredon Group (intrusion-set)85- Gelsemium (malware)86- HermeticWizard (malware)87- InvisiMole (malware)88- Kimsuky (intrusion-set)89- Latrodectus (malware)90- Medusa Group (intrusion-set)91- Milan (malware)92- MuddyWater (intrusion-set)93- Neoichor (malware)94- POWERSTATS (malware)95- Ramsay (malware)96- Raspberry Robin (malware)97- RustyWater (malware)98- SILENTTRINITY (tool)99- STATICPLUGIN (malware)100101## Recommended output pattern102103When responding with this skill, structure the answer as:104105- Assessment: whether the evidence supports this ATT&CK mapping and why.106- Evidence: specific indicators, logs, behaviors, and assumptions.107- Detection: telemetry sources, analytic logic, and tuning considerations.108- Response: containment, eradication, recovery, and validation actions.109- Coverage gaps: missing logs, sensors, controls, or environmental details.110- References: include the ATT&CK URL and any user-provided evidence references.