Windows Registry Modification in Security Center AV Provider Keys (ProductEXE/DisplayName/ReportingExe)

Alerts on registry modifications under Security Center AV Provider keys that update antivirus product fields like ProductEXE and DisplayName.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2026-10-18
Updated
2026-10-19

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 set activity targeting Microsoft Security Center AV Provider keys by matching TargetObject paths that end with ProductEXE, DisplayName, or ReportingExe. These values are used to represent installed antivirus/security product information, so unauthorized or unexpected changes may indicate attempts to impair or misrepresent security tooling. It relies on registry set telemetry including the TargetObject path and the modifying process details captured in the event.

Related detections9 linkedT1685 — drag to rearrange
Malicious BYOVD EDR Kill via Renamed GMER Driver by Agonizing Serpens
Malicious ThrottleStop Vulnerable Driver Load for Defense Evasion
Malicious WinRing0 Vulnerable Driver Load for Coin Mining
Windows Security Log: Defendnot scheduled task (defendnot) persistence via --from-autorun
PowerShell: Defendnot hacktool installation via one-liner fetching dnot.sh
Suspicious Security Software Removal Batch Script Execution
Suspicious Silent Security Product Uninstaller Execution
Malicious Antivirus Removal via WMIC Product Uninstall
Malicious Defender Exclusion Added via Add-MpPreference (via process_creation)
Windows Registry Modification in Security Center AV Provider Keys (ProductEXE/DisplayName/ReportingExe)
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.