KernelCallbackTable
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.
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("NtQueryInformationProcess", "ntdll.dll")
or ProcessCommandLine has_any ("VirtualAllocEx", "WriteProcessMemory", "NtWriteVirtualMemory")
| join kind=inner (
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("explorer.exe", "notepad.exe", "calc.exe", "mspaint.exe")
| where not(FolderPath startswith "C:\\Windows\\System32")
| project DeviceName, ParentProcessId=ProcessId, ParentFileName=FileName, ParentPath=FolderPath
) on DeviceName
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine,
ParentFileName, ParentPath
| sort by Timestamp desc
| union (
DeviceEvents
| where Timestamp > ago(24h)
| where ActionType == "ProcessInjection" or ActionType == "RemoteThreadInjection"
| where TargetProcessFileName in~ ("explorer.exe", "notepad.exe", "iexplore.exe", "chrome.exe", "firefox.exe")
| project Timestamp, DeviceName, AccountName=InitiatingProcessAccountName,
InitiatingProcessFileName, TargetProcessFileName, ActionType
)
| sort by Timestamp desc Data Sources
Required Tables
False Positives
- Legitimate accessibility software (screen readers, magnifiers) that interact with other process memory for UI automation
- Debug builds of applications that legitimately use WriteProcessMemory for inter-process communication
- Virtualization and container tools that may access process memory for management purposes
- Some game anti-cheat systems that inject DLLs into game processes
References (5)
- https://attack.mitre.org/techniques/T1574/013/
- https://blog.malwarebytes.com/threat-intelligence/2022/01/north-koreas-lazarus-apt-leverages-windows-update-client-github-in-latest-campaign/
- https://modexp.wordpress.com/2019/05/25/windows-injection-finspy/
- https://www.microsoft.com/security/blog/2018/03/01/finfisher-exposed-a-researchers-tale-of-defeating-traps-tricks-and-complex-virtual-machines/
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1574.013/T1574.013.md
Unlock Pro Content
Get the full detection package for T1574.013 including response playbook, investigation guide, and atomic red team tests.