Windows Registry: Suspicious Keyboard Layout Preload in User Session

Detects user-hive registry changes that preload Persian (Iranian) or Vietnamese keyboard layouts under Windows.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-10-12
Updated
2026-07-30

ATT&CK techniques

Resource Dev
  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 that include the Keyboard Layout Preload (and Substitutes) paths under the current user hive, with details matching specific layout identifiers (Persian/Iranian and Vietnamese). Loading keyboard layouts via these entries can support attacker interaction by aligning input methods with targeted environments or user expectations. It relies on registry set telemetry capturing TargetObject and Details fields for changes under the \\Keyboard Layout\\Preload and \\Keyboard Layout\\Substitutes locations.

Related detections9 linkedT1588.002 — drag to rearrange
Malicious Viper C2 Installation via f8x One-Liner Setup Script (via process_creation)
Windows RegistrySet: EulaAccepted set for renamed Sysinternals tools
Windows Registry Set: Sysinternals EULA Accepted Key for PUA Tool Execution
Windows Registry: Sysinternals Renamed Tool Execution Indicator via EulaAccepted Key
Windows Hacktool Execution via PE Metadata Company Field
Windows Hacktool Execution Flagged by Imphash in Process Creation
Windows: Renamed Sysinternals DebugView Process Execution
Windows Registry Key Created: Sysinternals EULA Acceptance
Windows: Command-line execution using Sysinternals -accepteula flag
Windows Registry: Suspicious Keyboard Layout Preload in User Session
Pivot detection · T1588.002 · 9 related

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