Suspicious GitHub Self-Hosted Runner Registration via Audit Log (via github)

PremiumReviewedSigma · Medium · v1
Product
github
Service
audit
Author
HuntRule
Published
2026-10-28
Updated
2026-10-28

ATT&CK techniques

Initial Access → Priv Esc
  1. Recon

  2. Resource Dev

  3. Execution

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects the registration of a self-hosted runner in GitHub audit logs. Threat actors abuse self-hosted runner registration to plant a backdoor that executes attacker controlled workflows on infrastructure they should not control. Unexpected runner registration events should be validated against approved automation changes.

Related detections9 linkedT1543 — drag to rearrange
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Malicious Fire Ant Hypervisor Backdoor Artifacts on ESXi and vCenter (via file_event)
Suspicious D-Bus System Service Persistence File Creation
Malicious BRICKSTORM Backdoor Execution via Masqueraded Binary Path
Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py
Malicious Linux XorDDoS gcc.pid Device Marker File via file_event
Windows Code Integrity: Blocked Driver Load Due to Revoked Certificate (Event ID 3023)
Windows PUA System Informer Driver Load via SystemInformer.sys
System Informer Execution on Windows Process Creation
Suspicious GitHub Self-Hosted Runner Registration via Audit Log (via github)
Pivot detection · T1543 · 9 related

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