T1546.011 Google Chronicle · YARA-L

Detect Application Shimming in Google Chronicle

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by application shims. The Microsoft Windows Application Compatibility Infrastructure/Framework (Application Shim) was created to allow for backward compatibility of software as the operating system codebase changes over time. The SDB (Shim DataBase) stores fix entries and shims. Malicious shim databases can be installed by adversaries using sdbinst.exe. Custom shims can be written to intercept and redirect API calls to inject malicious code into otherwise legitimate processes. This allows adversaries to apply persistent fixes to legitimate applications that execute when those applications run.

MITRE ATT&CK

Tactic
Privilege Escalation Persistence
Technique
T1546 Event Triggered Execution
Sub-technique
T1546.011 Application Shimming
Canonical reference
https://attack.mitre.org/techniques/T1546/011/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule application_shimming_t1546_011 {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects Application Shimming (T1546.011) via sdbinst.exe execution, AppCompatFlags registry modification, or .sdb file creation outside Windows AppPatch"
    mitre_attack_tactic = "Persistence, Privilege Escalation"
    mitre_attack_technique = "T1546.011"
    severity = "HIGH"
    confidence = "HIGH"
    created = "2026-04-20"

  events:
    (
      // sdbinst.exe process execution
      ($e.metadata.event_type = "PROCESS_LAUNCH" and
       re.regex($e.target.process.file.full_path, `(?i)sdbinst\.exe$`))
      or
      // AppCompatFlags registry modification
      ($e.metadata.event_type = "REGISTRY_MODIFICATION" and
       (
         re.regex($e.target.registry.registry_key, `(?i)AppCompatFlags\\(Custom|InstalledSDB)`) or
         re.regex($e.target.registry.registry_key, `(?i)AppCompatFlags.*(Custom|InstalledSDB)`)
       ))
      or
      // .sdb file created outside Windows AppPatch
      ($e.metadata.event_type = "FILE_CREATION" and
       re.regex($e.target.file.full_path, `(?i)\.sdb$`) and
       not re.regex($e.target.file.full_path, `(?i)Windows\\AppPatch`))
    )

  condition:
    $e
}
high severity high confidence

Chronicle YARA-L 2.0 rule detecting Application Shimming persistence (T1546.011) by monitoring for sdbinst.exe process launches, AppCompatFlags registry key modifications (Custom/InstalledSDB), and .sdb shim database file creation outside the legitimate Windows AppPatch directory using UDM event fields.

Data Sources

Google Chronicle SIEMWindows Event Forwarding to ChronicleChronicle Unified Data Model (UDM)

Required Tables

UDM Events (PROCESS_LAUNCH, REGISTRY_MODIFICATION, FILE_CREATION)

False Positives & Tuning

  • Software vendors distributing applications with embedded compatibility shims will trigger both the sdbinst.exe process event and AppCompatFlags registry modification conditions as part of their standard installer execution.
  • IT administrators using the Microsoft Application Compatibility Toolkit to apply organization-wide compatibility fixes will generate sustained streams of these events during controlled deployment windows.
  • Endpoint Detection and Response products that leverage Windows shim infrastructure as part of their behavioral monitoring may write non-malicious .sdb files and registry entries matching this rule's conditions.
Download portable Sigma rule (.yml)

Other platforms for T1546.011


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Install Custom Shim Database with sdbinst.exe

    Expected signal: Process creation for sdbinst.exe with the SDB file path argument. File creation event for argus_test.sdb in Temp directory. Registry modification to AppCompatFlags\InstalledSDB adding a new GUID key. Process creation event for sdbinst.exe is the primary detection trigger.

  2. Test 2Query Installed Shim Databases

    Expected signal: Process creation for reg.exe querying AppCompatFlags keys. Read-only operation. Output shows all installed SDB GUIDs and their file paths.

  3. Test 3Create Shim Database File Outside AppPatch

    Expected signal: File creation event (Sysmon 11): TargetFilename ends with .sdb and path contains Temp, not Windows\AppPatch. This triggers the SDB_FILE_CREATED detection vector.

Unlock Pro Content

Get the full detection package for T1546.011 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections