Cross-source coverage
T1546.001 / ATT&CK
Event Triggered Execution: Change Default File Association
9 rules across 4 sources.
1 deprecated hidden · include
From MITRE ATT&CK 19.2
Adversaries may establish persistence by executing malicious content triggered by a file type association. When a file is opened, the default program used to open the file (also called the file association or handler) is checked. File association selections are stored in the Windows Registry and can be edited by users, administrators, or programs that have Registry access or by administrators using the built-in assoc utility. Applications can modify the file association for a given file extension to call an arbitrary program when a file with the given extension is opened.
System file associations are listed under HKEY_CLASSES_ROOT\.[extension], for example HKEY_CLASSES_ROOT\.txt. The entries point to a handler for that extension located at HKEY_CLASSES_ROOT\\[handler]. The various commands are then listed as subkeys underneath the shell key at HKEY_CLASSES_ROOT\\[handler]\shell\\[action]\command. For example:
HKEY_CLASSES_ROOT\txtfile\shell\open\commandHKEY_CLASSES_ROOT\txtfile\shell\print\commandHKEY_CLASSES_ROOT\txtfile\shell\printto\command
The values of the keys listed are commands that are executed when the handler opens the file extension. Adversaries can modify these values to continually execute arbitrary commands.
- Tactics
- Privilege Escalation · Persistence
- Platforms
- Windows
- Telemetry
-
WinEventLog:SysmonWinEventLog:Security
How MITRE says to detect it DET0061
Detect Default File Association Hijack via Registry & Execution Correlation on Windows
Windows Analytic 0170
Detects modification of registry keys used for default file handlers, followed by anomalous process execution from user-initiated file opens. This includes tracking changes under HKCU and HKCR for file extension mappings, and correlating them with new or suspicious handler paths launching unusual child processes (e.g., PowerShell, cmd, wscript).
WinEventLog:SysmonEventCode=13, 14WinEventLog:SysmonEventCode=1WinEventLog:SecurityEventCode=4672
SigmaHQ/sigma
5 rules| Detection | Severity | Format |
|---|---|---|
| Change Default File Association To Executable Via Assoc | High | Sigma |
| Shell Open Registry Keys Manipulation | High | Sigma |
| Registry Modification of MS-settings Protocol Handler | Medium | Sigma |
| Suspicious Shell Open Command Registry Modification | Medium | Sigma |
| Change Default File Association Via Assoc | Low | Sigma |
splunk/security_content
2 rules| Detection | Severity | Format |
|---|---|---|
| Windows Change File Association Command To Notepad | Undefined | SPL |
| Windows New Default File Association Value Set | Undefined | SPL |
elastic/protections-artifacts
1 rule| Detection | Severity | Format |
|---|---|---|
| Suspicious Shell Extension Handler Registry Modification | Undefined | Elastic TOML |
socfortress/Wazuh-Rules
1 rule| Detection | Severity | Format |
|---|---|---|
| Change Default File Association via \Explorer\FileExts (T1546.001) | High | Wazuh XML |