Detect Parent PID Spoofing in Splunk
Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. By calling CreateProcess with a PROC_THREAD_ATTRIBUTE_PARENT_PROCESS entry in the process attribute list, an attacker can assign any running process as the apparent parent of the newly spawned child. Security tools that rely on parent-child process lineage for detection see only the spoofed parent, masking the true origin. This technique is also exploited for privilege escalation: by opening a handle to a SYSTEM-level process such as lsass.exe and using it as the spoofed parent, the child process inherits the SYSTEM access token. Used in the wild by Cobalt Strike, KONNI, PipeMon, and DarkGate.
MITRE ATT&CK
- Technique
- T1134 Access Token Manipulation
- Sub-technique
- T1134.004 Parent PID Spoofing
- Canonical reference
- https://attack.mitre.org/techniques/T1134/004/
SPL Detection Query
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| eval ParentImageShort=lower(replace(ParentImage, ".*\\\\", ""))
| eval ImageShort=lower(replace(Image, ".*\\\\", ""))
| eval IsHighValueSpoofParent=if(match(ParentImageShort, "^(lsass|wininit|smss|csrss|winlogon|services)\.exe$"), 1, 0)
| eval IsSuspiciousChild=if(match(ImageShort, "^(cmd|powershell|pwsh|rundll32|regsvr32|mshta|wscript|cscript|msbuild|certutil|bitsadmin|cmstp|installutil)\.exe$"), 1, 0)
| eval IsHighValueAndSuspicious=if(IsHighValueSpoofParent=1 AND IsSuspiciousChild=1, 1, 0)
| eval IsIntegrityMismatch=if(IntegrityLevel="System" AND NOT match(ParentImageShort, "^(lsass|wininit|smss|csrss|winlogon|services|system|ntoskrnl)\.exe$") AND IsSuspiciousChild=1, 1, 0)
| eval IsExplorerSystemChild=if(ParentImageShort="explorer.exe" AND IntegrityLevel="System", 1, 0)
| eval SpoofScore=IsHighValueAndSuspicious + IsIntegrityMismatch + IsExplorerSystemChild
| where SpoofScore > 0
| eval SpoofBranch=case(
IsHighValueAndSuspicious=1 AND IsIntegrityMismatch=1, "HighPrivilege+IntegrityMismatch",
IsHighValueAndSuspicious=1, "HighPrivilegeParentSpawn",
IsIntegrityMismatch=1, "IntegrityMismatchElevation",
IsExplorerSystemChild=1, "ExplorerSystemChild",
true(), "MultipleIndicators"
)
| table _time, host, User, Image, CommandLine, ParentImage, ParentCommandLine, IntegrityLevel, ProcessId, ProcessGuid, SpoofBranch, SpoofScore
| sort - _timeDetects PPID spoofing via Sysmon Event ID 1 (Process Creation) using three scored detection branches: (1) system processes (lsass.exe, wininit.exe, smss.exe, csrss.exe, winlogon.exe) appearing as parents of shells or LOLBins; (2) SYSTEM-integrity child processes spawned by non-SYSTEM parents — normal Windows only creates SYSTEM children from SYSTEM or kernel contexts; (3) explorer.exe as the parent of any SYSTEM-integrity process. Each branch contributes to a cumulative SpoofScore for analyst prioritization, with the SpoofBranch field identifying which detection logic triggered.
Data Sources
Required Sourcetypes
False Positives & Tuning
- UAC consent.exe elevation flows may produce system-process parent assignments during token handoff in some Windows 10/11 configurations
- Security products (CrowdStrike, SentinelOne, Carbon Black) using kernel-level process injection for protection modules may appear as anomalous parent-child pairs
- Windows Subsystem for Linux (WSL2) process trees can produce unusual parent-child relationships that resemble PPID anomalies when crossing the WSL boundary
- SCCM/Intune management agents deploying scripts via CcmExec.exe or the Intune Management Extension service may produce shell spawns with unexpected service process parents
Other platforms for T1134.004
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1PPID Spoofing via PowerShell P/Invoke — Explorer Parent
Expected signal: Sysmon Event ID 1: cmd.exe process creation with ParentImage=<path>\explorer.exe and ParentProcessId matching the selected explorer.exe PID. The actual spawning process (PowerShell) does NOT appear as ParentImage. Sysmon Event ID 10: may capture OpenProcess against explorer.exe from PowerShell with GrantedAccess=0x0080. Security Event ID 4688 (if audit enabled): CreatorProcessId=PowerShell's PID, ParentProcessId=explorer.exe's PID — the mismatch confirms spoofing.
- Test 2PPID Spoofing for Privilege Escalation — LSASS as Spoofed Parent
Expected signal: Sysmon Event ID 1: cmd.exe with ParentImage=lsass.exe, ParentProcessId=LSASS PID, IntegrityLevel=System. Sysmon Event ID 10: SourceImage=PowerShell accessing TargetImage=lsass.exe with GrantedAccess=0x0080. Security Event ID 4672: Special privilege logon for the SYSTEM session inherited by cmd.exe. Security Event ID 4688 (if audit enabled): CreatorProcessId=PowerShell PID vs ParentProcessId=LSASS PID — mismatch is the definitive forensic artifact.
- Test 3Cobalt Strike Spawn-To Simulation — Rundll32 Under Explorer
Expected signal: Sysmon Event ID 1: rundll32.exe creation with ParentImage=explorer.exe and ParentProcessId matching the selected explorer.exe PID. Sysmon Event ID 10: OpenProcess from PowerShell against explorer.exe with GrantedAccess=0x0080. The rundll32.exe -> explorer.exe parent relationship is the canonical Cobalt Strike PPID spoofing telemetry signature seen in real incident response engagements.
- Test 4PPID Spoofing Detection Validation — Sysmon ParentProcessId vs Security 4688 CreatorProcessId
Expected signal: Sysmon Event ID 1: cmd.exe with ParentImage=svchost.exe, ParentProcessId=<svchost PID>. Security Event ID 4688 (requires audit process creation + command line enabled): CreatorProcessId=<PowerShell PID>, ParentProcessId=<svchost PID> — the mismatch between Creator and Parent is the definitive PPID spoof indicator. The test outputs exact PID values needed for manual SIEM correlation to confirm the discrepancy is visible in your environment.
References (8)
- https://attack.mitre.org/techniques/T1134/004/
- https://blog.didierstevens.com/2009/11/22/quickpost-selectmyparent-or-playing-with-the-windows-process-tree/
- https://www.countercept.com/blog/detecting-parent-pid-spoofing/
- https://blog.xpnsec.com/becoming-system/
- https://blog.christophetd.fr/building-an-office-macro-to-spoof-process-parent-and-command-line/
- https://docs.microsoft.com/windows/desktop/ProcThread/process-creation-flags
- https://www.securityinbits.com/malware-analysis/parent-pid-spoofing-stage-2-ataware-ransomware-part-3
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1134.004/T1134.004.md
Unlock Pro Content
Get the full detection package for T1134.004 including response playbook, investigation guide, and atomic red team tests.