MITRE ATT&CK T1027.014: Polymorphic Code
When to use this skill
Use this skill when the task involves T1027.014, Polymorphic Code, 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: T1027.014
- Technique name: Polymorphic Code
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1027/014
- Tactics: stealth
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may utilize polymorphic code (also known as metamorphic or mutating code) to evade detection. Polymorphic code is a type of software capable of changing its runtime footprint during code execution.(Citation: polymorphic-blackberry) With each execution of the software, the code is mutated into a different version of itself that achieves the same purpose or objective as the original. This functionality enables the malware to evade traditional signature-based defenses, such as antivirus and antimalware tools.(Citation: polymorphic-sentinelone)
Other obfuscation techniques can be used in conjunction with polymorphic code to accomplish the intended effects, including using mutation engines to conduct actions such as Software Packing, Command Obfuscation, or Encrypted/Encoded File.(Citation: polymorphic-linkedin)(Citation: polymorphic-medium)
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
- Antivirus/Antimalware
- Behavior Prevention on Endpoint
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
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.
ATT&CK contributors
- TruKno
- Ye Yint Min Thu Htut, Active Defense Team, DBS Bank
1---2name: attack-ent-t1027-014-polymorphic-code3description: "Analyze MITRE ATT&CK T1027.014 Polymorphic Code in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1027.014, Polymorphic Code, or enterprise ATT&CK. Adversaries may utilize polymorphic code (also known as metamorphic or mutating code) to evade detection."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-t1027-014-polymorphic-code7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1027.01410 attack_stix_id: attack-pattern--b577dfc1-0177-4522-8d5a-782127c8592b11 attack_version: "2.0"12 attack_modified: "2026-04-15T22:20:58.199Z"13---1415# MITRE ATT&CK T1027.014: Polymorphic Code1617## When to use this skill1819Use this skill when the task involves T1027.014, Polymorphic Code, 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: T1027.01425- Technique name: Polymorphic Code26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1027/01428- Tactics: stealth29- Platforms: Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may utilize polymorphic code (also known as metamorphic or mutating code) to evade detection. Polymorphic code is a type of software capable of changing its runtime footprint during code execution.(Citation: polymorphic-blackberry) With each execution of the software, the code is mutated into a different version of itself that achieves the same purpose or objective as the original. This functionality enables the malware to evade traditional signature-based defenses, such as antivirus and antimalware tools.(Citation: polymorphic-sentinelone) 37Other obfuscation techniques can be used in conjunction with polymorphic code to accomplish the intended effects, including using mutation engines to conduct actions such as [Software Packing](https://attack.mitre.org/techniques/T1027/002), [Command Obfuscation](https://attack.mitre.org/techniques/T1027/010), or [Encrypted/Encoded File](https://attack.mitre.org/techniques/T1027/013).(Citation: polymorphic-linkedin)(Citation: polymorphic-medium)3839## Agent workflow40411. 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.422. 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.433. 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.444. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.455. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.466. 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.4748## Bundled resources4950- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.51- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.52- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.53- `templates/detection-brief.md`: detection engineering brief template.54- `templates/hunt-plan.md`: threat hunt plan template.55- `templates/incident-response-note.md`: incident response note template.56- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.57- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.58- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5960To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6162## Detection guidance6364No ATT&CK detection guidance was present in the source STIX object.6566## Useful telemetry and data sources6768- Not specified in the STIX object.6970## Mitigations to consider7172- Antivirus/Antimalware73- Behavior Prevention on Endpoint7475## Known threat context7677Use these examples only as contextual leads, not as proof that an observed event is this technique:7879- BendyBear (malware)8081## Recommended output pattern8283When responding with this skill, structure the answer as:8485- Assessment: whether the evidence supports this ATT&CK mapping and why.86- Evidence: specific indicators, logs, behaviors, and assumptions.87- Detection: telemetry sources, analytic logic, and tuning considerations.88- Response: containment, eradication, recovery, and validation actions.89- Coverage gaps: missing logs, sensors, controls, or environmental details.90- References: include the ATT&CK URL and any user-provided evidence references.9192## ATT&CK contributors9394- TruKno95- Ye Yint Min Thu Htut, Active Defense Team, DBS Bank