MITRE ATT&CK T1055.002: Portable Executable Injection
When to use this skill
Use this skill when the task involves T1055.002, Portable Executable Injection, 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: T1055.002
- Technique name: Portable Executable Injection
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1055/002
- Tactics: privilege-escalation, stealth
- Platforms: Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges. PE injection is a method of executing arbitrary code in the address space of a separate live process.
PE injection is commonly performed by copying code (perhaps without a file on disk) into the virtual address space of the target process before invoking it via a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread or additional code (ex: shellcode). The displacement of the injected code does introduce the additional requirement for functionality to remap memory references. (Citation: Elastic Process Injection July 2017)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via PE injection may also evade detection from security products since the execution is masked under a legitimate process.
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
- Behavior Prevention on Endpoint
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- 3CX Supply Chain Attack (campaign)
- Brute Ratel C4 (tool)
- Carbanak (malware)
- DUSTPAN (malware)
- Gootloader (malware)
- Gorgon Group (intrusion-set)
- GreyEnergy (malware)
- Havoc (malware)
- InvisiMole (malware)
- Lizar (malware)
- Pikabot (malware)
- Rocke (intrusion-set)
- RustyWater (malware)
- SPAWNCHIMERA (malware)
- Zeus Panda (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-t1055-002-portable-executable-injection3description: "Analyze MITRE ATT&CK T1055.002 Portable Executable Injection in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1055.002, Portable Executable Injection, or enterprise ATT&CK. Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges."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-t1055-002-portable-executable-injection7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1055.00210 attack_stix_id: attack-pattern--806a49c4-970d-43f9-9acc-ac0ee11e666211 attack_version: "2.0"12 attack_modified: "2026-04-15T22:28:35.452Z"13---1415# MITRE ATT&CK T1055.002: Portable Executable Injection1617## When to use this skill1819Use this skill when the task involves T1055.002, Portable Executable Injection, 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: T1055.00225- Technique name: Portable Executable Injection26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1055/00228- Tactics: privilege-escalation, stealth29- Platforms: Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges. PE injection is a method of executing arbitrary code in the address space of a separate live process. 3738PE injection is commonly performed by copying code (perhaps without a file on disk) into the virtual address space of the target process before invoking it via a new thread. The write can be performed with native Windows API calls such as <code>VirtualAllocEx</code> and <code>WriteProcessMemory</code>, then invoked with <code>CreateRemoteThread</code> or additional code (ex: shellcode). The displacement of the injected code does introduce the additional requirement for functionality to remap memory references. (Citation: Elastic Process Injection July 2017) 3940Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via PE injection may also evade detection from security products since the execution is masked under a legitimate process.4142## Agent workflow43441. 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.452. 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.463. 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.474. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.485. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.496. 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.5051## Bundled resources5253- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.54- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.55- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.56- `templates/detection-brief.md`: detection engineering brief template.57- `templates/hunt-plan.md`: threat hunt plan template.58- `templates/incident-response-note.md`: incident response note template.59- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.60- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.61- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6263To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6465## Detection guidance6667No ATT&CK detection guidance was present in the source STIX object.6869## Useful telemetry and data sources7071- Not specified in the STIX object.7273## Mitigations to consider7475- Behavior Prevention on Endpoint7677## Known threat context7879Use these examples only as contextual leads, not as proof that an observed event is this technique:8081- 3CX Supply Chain Attack (campaign)82- Brute Ratel C4 (tool)83- Carbanak (malware)84- DUSTPAN (malware)85- Gootloader (malware)86- Gorgon Group (intrusion-set)87- GreyEnergy (malware)88- Havoc (malware)89- InvisiMole (malware)90- Lizar (malware)91- Pikabot (malware)92- Rocke (intrusion-set)93- RustyWater (malware)94- SPAWNCHIMERA (malware)95- Zeus Panda (malware)9697## Recommended output pattern9899When responding with this skill, structure the answer as:100101- Assessment: whether the evidence supports this ATT&CK mapping and why.102- Evidence: specific indicators, logs, behaviors, and assumptions.103- Detection: telemetry sources, analytic logic, and tuning considerations.104- Response: containment, eradication, recovery, and validation actions.105- Coverage gaps: missing logs, sensors, controls, or environmental details.106- References: include the ATT&CK URL and any user-provided evidence references.