Windows GitHub Self-Hosted Runner Execution via Runner.Worker and Runner.Listener

Alerts on Windows process activity from GitHub self-hosted runner Worker/Listener indicating spawnclient or run/configure operations.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Daniel Koifman (KoifSec) (SigmaHQ), DRL 1.1
Published
2025-11-29
Updated
2026-07-31

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows process executions associated with GitHub self-hosted runners by matching the Runner.Worker.exe spawnclient activity or the Runner.Listener.exe configure and run activity. Such runner processes can enable persistence and code execution within local infrastructure because they are designed to interact with CI workflows and, in many environments, access internal resources and secrets. It relies on process creation telemetry, specifically the process image name endings, OriginalFileName values, and command-line content.

Related detections9 linkedT1102.002 — drag to rearrange
Suspicious Python Process Establishing PostgreSQL Command and Control Channel
Malicious Dropbox Cloud C2 via Spoofed Googlebot User Agent
Suspicious UNC1549 Azure C2 Beacon to News Notifications URI Pattern (via proxy)
Suspicious Project CAV3RN AzureCommunication.dll Load (via image_load)
Suspicious Google API DNS Query From Temporary Directory Process Abused for C2
Possible WailingCrab MQTT C2 to Public Broker (via network_connection)
Malicious OilRig OAuth Application Sign-In via Azure (via azure)
Suspicious Outbound Network Connection from explorer.exe
Suspicious Instant Messenger Client Spawning Script Interpreter (via process_creation)
Windows GitHub Self-Hosted Runner Execution via Runner.Worker and Runner.Listener
Pivot detection · T1102.002 · 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.