aol.pm

Image File Execution Options Injection

Subtechnique · ATTACK:enterprise:T1546.012

Attributed source ↗ · Plaintext record · Complete record and assertions JSON

Inspect structured metadata and provenance
{
  "id": "ATTACK:enterprise:T1546.012",
  "title": "Image File Execution Options Injection",
  "type": "Subtechnique",
  "source_url": "https://attack.mitre.org/techniques/T1546/012",
  "snapshot": "enterprise-attack-20.0.json",
  "status": "active",
  "rights": "Source metadata only; source notices retained; no operational prose or payloads",
  "review_status": "machine-extracted; source-specific checks passed, editorial review pending",
  "stix_id": "attack-pattern--6d4a7fb3-5a24-42be-ae61-6728a2b581f6",
  "external_id": "T1546.012",
  "domain": "enterprise",
  "created": "2020-01-24T15:05:58.384Z",
  "modified": "2026-05-12T15:12:00.640Z",
  "version": "1.2",
  "aliases": [

  ],
  "tactics": [
    "privilege-escalation",
    "persistence"
  ],
  "source_references": [
    {
      "source_name": "FSecure Hupigon",
      "url": "https://www.f-secure.com/v-descs/backdoor_w32_hupigon_emv.shtml"
    },
    {
      "source_name": "Elastic Process Injection July 2017",
      "url": "https://www.endgame.com/blog/technical-blog/ten-process-injection-techniques-technical-survey-common-and-trending-process"
    },
    {
      "source_name": "Microsoft Silent Process Exit NOV 2017",
      "url": "https://docs.microsoft.com/windows-hardware/drivers/debugger/registry-entries-for-silent-process-exit"
    },
    {
      "source_name": "Microsoft GFlags Mar 2017",
      "url": "https://docs.microsoft.com/windows-hardware/drivers/debugger/gflags-overview"
    },
    {
      "source_name": "Oddvar Moe IFEO APR 2018",
      "url": "https://oddvar.moe/2018/04/10/persistence-using-globalflags-in-image-file-execution-options-hidden-from-autoruns-exe/"
    },
    {
      "source_name": "Microsoft Dev Blog IFEO Mar 2010",
      "url": "https://blogs.msdn.microsoft.com/mithuns/2010/03/24/image-file-execution-options-ifeo/"
    },
    {
      "source_name": "Symantec Ushedix June 2008",
      "url": "https://www.symantec.com/security_response/writeup.jsp?docid=2008-062807-2501-99&tabid=2"
    },
    {
      "source_name": "Tilbury 2014",
      "url": "https://web.archive.org/web/20200730053039/https://www.crowdstrike.com/blog/registry-analysis-with-crowdresponse/"
    }
  ]
}

Explicit source assertions (4)

First 80 shown here; the complete set is in this record’s JSON and plaintext. Each relationship retains its source and locator. No inferred relationships are added.

ATTACK:enterprise:S0559 → uses → ATTACK:enterprise:T1546.012

MITRE ATT&CK: Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.

Assertion source · Locator: relationship--78fce2a1-4d92-4e67-8e9b-c684f33b4536

Microsoft Deep Dive Solorigate January 2021

ATTACK:enterprise:T1546.012 → subtechnique-of → ATTACK:enterprise:T1546

MITRE ATT&CK: Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.

Assertion source · Locator: relationship--8a468c91-7863-4569-8e5f-a71cd565478e

ATTACK:enterprise:S0461 → uses → ATTACK:enterprise:T1546.012

MITRE ATT&CK: Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.

Assertion source · Locator: relationship--91e86813-270d-4ee6-8dff-9b87e3d9fae4

Proofpoint TA505 October 2019

ATTACK:enterprise:C0032 → uses → ATTACK:enterprise:T1546.012

MITRE ATT&CK: Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.

Assertion source · Locator: relationship--df4d5d3b-67b7-4af5-adb3-ee83b5f44c5b

FireEye TRITON 2019

Provided as is, for information only, with no warranty and no liability. Not legal or professional advice. Security and radio material is for authorized, lawful use only. Full disclaimer.

Visits are logged on our own server: IP address, browser and device details, and pages viewed. We use them to understand traffic and spot attacks, and never share or sell them.