huntrule

Windows Registry: Uncommon IME File Value in Keyboard Layouts Path

Alerts on Control\Keyboard Layouts\ registry values named "Ime File" that reference non-.ime extensions.

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
AnalysisDetection

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 Windows registry writes that set the value name "Ime File" under the Control\Keyboard Layouts\ path. Attackers can abuse the IME keyboard layout mechanism to cause a process to load a DLL associated with that registry configuration, following an input language change request. The detection relies on Windows registry set telemetry, matching the registry key path and the presence of the "Ime File" value name, while filtering out entries that end with a known ".ime" extension.

Reporting behind it

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: Uncommon IME File Value in Keyboard Layouts Path
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.