{
  "type": "attack-pattern",
  "spec_version": "2.1",
  "id": "attack-pattern--b7c0e45f-0206-4f75-96e7-fe7edad3aaff",
  "created": "2022-03-30T18:50:43.393Z",
  "created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "revoked": false,
  "external_references": [
    {
      "source_name": "mitre-attack",
      "url": "https://attack.mitre.org/techniques/T1631",
      "external_id": "T1631"
    }
  ],
  "object_marking_refs": [
    "marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
  ],
  "modified": "2025-10-24T17:49:16.232Z",
  "name": "Process Injection",
  "description": "Adversaries may inject code into processes in order to evade process-based defenses or even elevate privileges. Process injection is a method of executing arbitrary code in the address space of a separate live process. 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 process injection may also evade detection from security products since the execution is masked under a legitimate process. \n\nBoth Android and iOS have no legitimate way to achieve process injection. The only way this is possible is by abusing existing root access or exploiting a vulnerability.",
  "kill_chain_phases": [
    {
      "kill_chain_name": "mitre-mobile-attack",
      "phase_name": "defense-evasion"
    },
    {
      "kill_chain_name": "mitre-mobile-attack",
      "phase_name": "privilege-escalation"
    }
  ],
  "x_mitre_attack_spec_version": "3.2.0",
  "x_mitre_deprecated": false,
  "x_mitre_domains": [
    "mobile-attack"
  ],
  "x_mitre_is_subtechnique": false,
  "x_mitre_modified_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "x_mitre_platforms": [
    "Android",
    "iOS"
  ],
  "x_mitre_version": "1.1",
  "x_mitre_tactic_type": [
    "Post-Adversary Device Access"
  ]
}