Windows: Root Certificate Added Using certutil.exe -addstore

Flags certutil.exe executions that use -addstore with root-related parameters to install a certificate.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
oscd.community, @redcanary, Zach Stanford @svch0st (SigmaHQ), DRL 1.1
Published
2023-03-05
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows process executions of certutil.exe that include the -addstore flag and specify the root certificate store. Installing a root certificate can enable an attacker to reduce browser or TLS warning prompts when intercepting or proxying traffic to adversary-controlled sites. It relies on process creation telemetry, matching the image path/OriginalFileName and filtering on command-line content.

Related detections9 linkedT1553.004 — drag to rearrange
Suspicious Certutil Download and Certificate Installation via Living-off-the-Land
Suspicious Firefox Enterprise Root Certificate Trust Enabled
Malicious Root Certificate Installed via certutil addstore for AiTM Interception
Malicious Root Certificate Installation via certutil
Suspicious Root Certificate Installation via certutil (via process_creation)
Windows AD CS Denied Certificate Enrollment Requests (Event ID 53)
Windows: Root Certificate Installation via CertMgr.EXE (/add root)
Linux Package Installation via apt/yum/rpm/dpkg with Networking Tools Keywords
Windows Process Creation: Suspicious X509Enrollment.CBinaryConverter Execution
Windows: Root Certificate Added Using certutil.exe -addstore
Pivot detection · T1553.004 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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