Windows: Suspicious Service Installation via Registry ImagePath Outside system32

Alerts on NalDrv/PROCEXP152 service ImagePath registry entries configured outside the expected system32 driver path.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
xknow (@xknow_infosec), xorxes (@xor_xes) (SigmaHQ), DRL 1.1
Published
2019-04-08
Updated
2026-07-30

ATT&CK techniques

  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 flags registry changes indicating installation of NalDrv or PROCEXP152 Windows services where the configured ImagePath points outside the Windows\system32\Drivers\PROCEXP152.SYS location. Such service installation can be used by attackers to persist or load components from non-standard locations, potentially evading normal expectations for system binaries. It relies on registry set telemetry for service ImagePath values under HKLM\System\CurrentControlSet\Services\<service>.

Related detections9 linkedT1685 — drag to rearrange
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks
Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware
Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)
Suspicious Security Product Uninstall via wmic product call uninstall
Windows: Suspicious Service Installation via Registry ImagePath Outside system32
Pivot detection · T1685 · 9 related

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