Windows Registry Fax Device Provider ImageName changed to load external DLL

Alerts when Fax Device Providers\ImageName registry values change in a way consistent with DLL-loading persistence.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-07-17
Updated
2026-07-30

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags registry changes under the Fax device provider path where an ImageName value is set, indicating a possible Fax DLL load persistence mechanism upon service restart. Attackers may use this to cause a service to load a chosen DLL, helping maintain execution across restarts while blending into expected system component configuration. Detection relies on Windows registry set telemetry matching the targeted Fax provider subkeys and ImageName entries, while excluding cases where the ImageName points to %systemroot%\system32\fxst30.dll.

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Windows Registry Fax Device Provider ImageName changed to load external DLL
Pivot detection · T1112 · 9 related

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