Windows Registry: New ODBC Driver Registration in Suspicious Path

Alerts when Windows registers a new ODBC driver under the ODBCINST.INI area with details pointing to suspicious filesystem paths.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-05-23
Updated
2026-07-30

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags registry entries for newly registered ODBC drivers and setups whose driver-related strings contain paths commonly associated with staging, writable locations, or unusual system subfolders. Attackers can use ODBC driver registration as a persistence mechanism or to execute malicious logic via legitimate database connectivity components. The detection relies on registry set event telemetry that includes the TargetObject and Details fields for the ODBCINST.INI driver registration location.

Related detections9 linkedT1003 — drag to rearrange
Malicious NTDS Credential Dump via Ntdsutil IFM Snapshot (via process_creation)
Suspicious Mimilite Credential Dumper Execution Writing KB-Named Output
Malicious InternalMonologue NTLM Downgrade Execution via process_creation
Suspicious Modification of msDS-KeyCredentialLink for Shadow Credential Abuse
Possible OxideHarvest Stealer Execution via Combined Short Flag Set
Suspicious Credential Dump Attempt via Task Manager (via process_creation)
Suspicious Ivanti EPMM Database Dump via mysqldump with .mifpp Credentials (via process_creation)
Suspicious Credential Dump via lsa.exe Debug Output
Malicious Wdigest Authentication Enabled - Reg via Command (via process_creation)
Windows Registry: New ODBC Driver Registration in Suspicious Path
Pivot detection · T1003 · 9 related

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