PATCHCORD Persistence via Registry Run Key BeaconBrowserHijack (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-10
Updated
2026-11-10

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects creation of the distinctively named Run key values used by the PATCHCORD and SHEETCORD backdoors to survive reboot in the Afghan telecom and South Asian critical-infrastructure campaign. Adversaries write BeaconBrowserHijack or SystemHelper under the CurrentVersion Run key to relaunch their implant at logon. Early detection surfaces the foothold before browser-shortcut hijacking and C2 tasking begin.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious XWorm Run Key Persistence Under XClient Value (via registry_set)
Malicious RAT Persistence via Windows Load Registry Value Pointing to Temp (via registry_set)
Malicious Registry Run Key Persistence Executing javaw with a PNG-Named JAR (via registry_set)
Malicious Node.js RAT Persistence via Run Key Referencing conhost Headless Loader (via registry_set)
Masquerading Registry Run Key Executing Regsvr32 on Public Directory Payload (via registry_set)
Masquerading Mustang Panda ZOHOMURK Persistence via Registry Run Key (via registry_set)
LOTUSLITE Persistence via Registry Run Key Lite360 (via registry_set)
Suspicious Autostart Persistence via Registry Run Key Pointing to a Script Interpreter (via registry_set)
GateDoor Run Key Persistence via MicrosoftOffice.Hub Value (via registry_set)
PATCHCORD Persistence via Registry Run Key BeaconBrowserHijack (via registry_set)
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.