huntrule

Suspicious SystemBC Persistence via Run Key to ProgramData Script

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-30
Updated
2026-10-30
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  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. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects a Run key autorun value referencing a script staged in ProgramData which the SystemBC component in this intrusion used to persist a SOCKS proxy across reboots and this matters because autostart entries pointing at scripts in ProgramData are a common malware persistence pattern and legitimate software normally registers under Program Files with signed binaries.

Reporting behind it

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Run Key Persistence Named AppResolver (via registry_set)
Suspicious Interlock RAT Persistence via HKCU Run Key Registration to AppData Payload (via process_creation)
Suspicious SOCKS Proxy Persistence via SystemBC PowerShell Run Key
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Persistence via Windows Update Service Run Key (via registry_set)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Run Key Persistence Named NvidiaDriverUpdate (via registry_set)
Suspicious HTA File Dropped into Startup Folder
Suspicious SystemBC Persistence via Run Key to ProgramData Script
Pivot detection · T1547.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.