Endpoint Detection and Response - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/endpoint-detection-and-response/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 24 Jul 2026 09:03:56 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDetection of Registry Keys Used for Persistencehttps://feed.craftedsignal.io/briefs/2026-07-registry-persistence/Fri, 24 Jul 2026 09:03:56 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-registry-persistence/This brief outlines a detection strategy for identifying modifications to Windows registry keys commonly used for persistence, including Run, Winlogon, and Image File Execution Options, enabling detection engineers to alert on unauthorized system startup entries for malicious code execution to prevent persistent access.This intelligence describes a detection capability designed to identify modifications to critical Windows registry keys frequently leveraged by threat actors for establishing and maintaining persistence on compromised systems. The detection monitors registry paths such as those associated with RunOnce, StartupApproved\Run, various Shell Folders, Winlogon entries, Appinit_Dlls, Image File Execution Options, and others known to automatically launch applications or services upon system startup or user logon. Unauthorized changes to these keys are a strong indicator of malicious activity, as they allow attackers to achieve persistent access, execute arbitrary code, or maintain control over compromised systems even after reboots, posing a severe threat to system integrity and security. This detection is crucial for identifying backdoor installations, malware loaders, and other forms of persistent access.

Impact

Successful modification of these registry keys by an attacker directly leads to persistent access on the compromised system. This means malicious code can execute automatically each time the system boots or a user logs in, granting the attacker a persistent foothold regardless of session or system restarts. The impact includes sustained control over the infected machine, potential for lateral movement, data exfiltration, or the deployment of further destructive payloads like ransomware. Organizations failing to detect and remediate such persistence mechanisms risk prolonged compromise and severe operational disruption, potentially leading to significant financial losses and reputational damage.

Recommendation

  • Deploy the Sigma rule provided in this brief to your SIEM and tune for your environment to detect suspicious registry modifications.
  • Enable Sysmon process-creation and registry logging (specifically Event ID 13 for RegistryEvent (Value Set)) to activate the rules above.
  • Monitor for changes to the specific registry paths listed in the Sigma rule's TargetObject selection, as these are critical for system startup and persistence.
  • Implement host-based intrusion prevention systems (HIPS) to block unauthorized modifications to sensitive registry keys mentioned in the detection section.
  • Regularly review logs related to registry modifications for endpoints identified in registry_keys_used_for_persistence to identify and triage potential persistence attempts.
]]>highadvisorypersistenceregistrywindowsendpointmalware