t1134-004-parent-pid-spoofing

name	T1134.004_parent-pid-spoofing
description	Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges.
category	configuration
version	18.1
author	cyberstrike-official
tags	["mitre-attack","enterprise","t1134.004","defense-evasion","privilege-escalation","windows","sub-technique"]
technique_id	T1134.004
tactic	defense-evasion
all_tactics	["defense-evasion","privilege-escalation"]
platforms	["Windows"]
mitre_url	https://attack.mitre.org/techniques/T1134/004
tech_stack	["windows"]
cwe_ids	["CWE-693"]
chains_with	["T1134","T1134.001","T1134.002","T1134.003","T1134.005"]
prerequisites	["T1134"]
severity_boost	{"T1134":"Chain with T1134 for deeper attack path","T1134.001":"Chain with T1134.001 for deeper attack path","T1134.002":"Chain with T1134.002 for deeper attack path"}

T1134.004 Parent PID Spoofing

Sub-technique of: T1134

High-Level Description

Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. New processes are typically spawned directly from their parent, or calling, process unless explicitly specified. One way of explicitly assigning the PPID of a new process is via the CreateProcess API call, which supports a parameter that defines the PPID to use. This functionality is used by Windows features such as User Account Control (UAC) to correctly set the PPID after a requested elevated process is spawned by SYSTEM (typically via svchost.exe or consent.exe) rather than the current user context.

Adversaries may abuse these mechanisms to evade defenses, such as those blocking processes spawning directly from Office documents, and analysis targeting unusual/potentially malicious parent-child process relationships, such as spoofing the PPID of PowerShell/Rundll32 to be explorer.exe rather than an Office document delivered as part of Spearphishing Attachment. This spoofing could be executed via Visual Basic within a malicious Office document or any code that can perform Native API.

Explicitly assigning the PPID may also enable elevated privileges given appropriate access rights to the parent process. For example, an adversary in a privileged user context (i.e. administrator) may spawn a new process and assign the parent as a process running as SYSTEM (such as lsass.exe), causing the new process to be elevated via the inherited access token.

Kill Chain Phase

• Defense Evasion (TA0005)
• Privilege Escalation (TA0004)

Platforms: Windows

What to Check

• Identify if Parent PID Spoofing technique is applicable to target environment
• Check Windows systems for indicators of Parent PID Spoofing
• Assess detection coverage (1 detection strategies)

How to Test

Atomic Red Team Tests

The following tests are from Atomic Red Team and provide actionable ways to test this technique:

Atomic Test 1: Parent PID Spoofing using PowerShell

This test uses PowerShell to replicates how Cobalt Strike does ppid spoofing and masquerade a spawned process. Upon execution, "Process C:\Program Files\Internet Explorer\iexplore.exe is spawned with pid ####" will be displayed and calc.exe will be launched.