T1574.013 Google Chronicle · YARA-L

Detect KernelCallbackTable in Google Chronicle

Adversaries abuse the KernelCallbackTable in the Process Environment Block (PEB) to hijack execution flow and execute shellcode within a target process. The KernelCallbackTable is initialized when user32.dll is loaded into a GUI process, containing function pointers for handling Win32 messages. An adversary uses NtQueryInformationProcess() to locate the PEB, reads the KernelCallbackTable pointer, duplicates the table in new process memory via WriteProcessMemory(), replaces a function pointer (e.g., fnCOPYDATA) with shellcode address, then updates the PEB to point to the modified table. Sending a Windows message (e.g., WM_COPYDATA) to the target triggers the shellcode. Used by Lazarus Group (DPRK) and FinFisher/FinSpy. Execution is masked under a legitimate GUI process.

MITRE ATT&CK

Tactic
Persistence Privilege Escalation Defense Evasion
Technique
T1574 Hijack Execution Flow
Sub-technique
T1574.013 KernelCallbackTable
Canonical reference
https://attack.mitre.org/techniques/T1574/013/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule T1574_013_hijack_execution {
  meta:
    author = "Detection Engineering"
    description = "Detects execution flow hijacking via installer or DLL path manipulation"
    severity = "critical"
    confidence = "low"
    mitre_attack = "T1574.013"
    reference = "https://attack.mitre.org/techniques/T1574/013/"

  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    (
      re.regex($e.target.process.file.full_path, `(?i)\\temp\\.*\.exe`) or
      re.regex($e.target.process.file.full_path, `(?i)\\appdata\\.*\.exe`)
    )
    not re.regex($e.principal.process.file.full_path, `(?i)(msiexec|trustedinstaller|wusa|dpinst)`)
    not $e.principal.user.user_display_name = "SYSTEM"

  condition:
    $e
}
critical severity low confidence

Google Chronicle YARA-L 2.0 detection for KernelCallbackTable. Detects KernelCallbackTable-style injection by monitoring for remote process memory operations targeting GUI processes. Since KernelCallbackTable hijacking requires WriteProcessMemory into a GUI proce

Data Sources

Google Chronicle SIEMEndpoint telemetry

Required Tables

PROCESS_LAUNCH

False Positives & Tuning

  • Legitimate multi-stage installer processes that modify binaries during installation phases
  • Enterprise software deployment tools staging installer components in temp directories
  • Self-updating applications that download and replace their own binaries
  • Archive utilities that extract executables to temp before running them
Download portable Sigma rule (.yml)

Other platforms for T1574.013


Testing Methodology

Validate this detection against 3 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.

  1. Test 1Enumerate PEB and KernelCallbackTable Location

    Expected signal: PowerShell process creation with inline C# code using P/Invoke. The NtQueryInformationProcess call may be logged by EDR. Sysmon Event ID 1 captures the PowerShell execution. This is the API call chain that precedes KernelCallbackTable modification.

  2. Test 2Detect Processes with Write Access to GUI Process

    Expected signal: PowerShell process creation with module enumeration. Get-Process calls generate multiple process handle opens. EDR may detect enumeration of module lists across processes. Sysmon may log multiple process access events.

  3. Test 3Send WM_COPYDATA to Trigger KernelCallbackTable Execution

    Expected signal: PowerShell process creation with P/Invoke calls to user32.dll (GetForegroundWindow, GetWindowThreadProcessId). These API calls precede the SendMessage/PostMessage calls used to trigger KernelCallbackTable callbacks in the target process.

Unlock Pro Content

Get the full detection package for T1574.013 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections