In-Memory Remote Thread Created With a Library-Loading Start Address (via create_remote_thread)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
create_remote_thread
Author
HuntRule
Published
2026-11-09
Updated
2026-11-09

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects a process creating a remote thread in another process whose start function is a library-loading routine such as LoadLibrary, a hallmark of classic DLL process injection. Process Injection is a top defense-evasion and privilege-escalation technique in the Red Canary Threat Detection Report, letting adversaries run code inside trusted processes to evade detection and access their memory. Alerting on library-loading remote threads surfaces injection attempts across tooling.

Related detections9 linkedT1055.001 — drag to rearrange
In-Memory gpupdate Spawned by Unusual Parent as Cobalt Strike Sacrificial Process (via process_creation)
Suspicious AppInit_DLLs Registry Modification for DLL Injection
Malicious DLL Injection via Mavinject Process Creation
Suspicious Process Injection via mavinject INJECTRUNNING
In-Memory Process Injection via Mavinject INJECTRUNNING (via process_creation)
Suspicious Service Reconfiguration of SessionEnv or IKEEXT for DLL Injection by EAGERBEE
Windows Process Creation: Renamed Mavinject32/64.EXE Execution
Windows Process Injection via Mavinject Using INJECTRUNNING Flag
Windows Process Execution and DLL Injection via Tracker.exe
In-Memory Remote Thread Created With a Library-Loading Start Address (via create_remote_thread)
Pivot detection · T1055.001 · 9 related

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