Windows process access matching Cobalt Strike BOF injection call trace

Flags suspicious Windows process access consistent with CobaltStrike BOF injection using ntdll/KERNELBASE call traces and high GrantedAccess.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-04
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process access events where the CallTrace matches a specific ntdll→KERNELBASE chain ending in an UNKNOWN address pattern, along with granted access values consistent with injection-style access. Attackers commonly use process injection to run code in the context of other processes while evading simpler defenses. It relies on process access telemetry that includes a CallTrace string and the GrantedAccess mask for the access attempt.

Related detections9 linkedT1106 — drag to rearrange
Nullsoft Scriptable Installer Script (NSIS) execution
Nullsoft Scriptable Installer Script (NSIS) file creation
Windows PowerShell ScriptBlock keyword match for WinPwn tool usage
Windows process command line matches WinPwn tool execution keywords
PowerShell Scripts Calling WinAPI DLLs on Windows
Windows PowerShell ScriptBlock WinAPI Function Calls
Windows Process Creation: WinAPI Function Names in Command-Line
Linux auditd: BPFDoor .pid or .lock file access in /var/run
Windows HandleKatz: Duplicate LSASS Handle via Process Access with Handle Duplication Rights
Windows process access matching Cobalt Strike BOF injection call trace
Pivot detection · T1106 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.