Windows Registry IME File Value Used from Suspicious Paths

Alerts on Windows keyboard layout "Ime File" registry entries pointing to suspicious writable directory paths.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-11-21
Updated
2026-07-30

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 writes or reads where the target contains both the Windows keyboard layouts key path segment and the value name "Ime File". It targets cases where the associated IME DLL path appears to reside in commonly abused writable locations such as Perflogs, public/temp directories, and user profile artifacts. Attackers may leverage IME keyboard layout loading to cause a process to load an attacker-controlled DLL after an input language change request. The detection relies on Windows registry telemetry capturing the target object path and value name.

Related detections9 linkedT1685 — drag to rearrange
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks
Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware
Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)
Suspicious Security Product Uninstall via wmic product call uninstall
Windows Registry IME File Value Used from Suspicious Paths
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.