Has utilized AutoIt malware scripts embedded in Microsoft Office documents or malicious links.1
AutoHotKey & AutoIT T1059.010
- Tactic
- Execution
- Platform
- Windows
- Version
- 1.1
- Created
- 29 March 2024
- Last modified
- 15 April 2025
- Contributors
- TruKno; Liran Ravich, CardinalOps; Serhii Melnyk, Trustwave SpiderLabs; Rahmat Nurfauzi, @infosecn1nja, PT Xynexis International; @_montysecurity
Adversaries may execute commands and perform malicious tasks using AutoIT and AutoHotKey automation scripts. AutoIT and AutoHotkey (AHK) are scripting languages that enable users to automate Windows tasks. These automation scripts can be used to perform a wide variety of actions, such as clicking on buttons, entering text, and opening and closing programs.[1][2]
AutoHotKey & AutoIT MITRE reference T1059.010
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 1 groups for this technique
5 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has utilized AutoIt malware scripts and AutoIt executables.12
Can use an AutoIT script to decrypt a payload file, load it into victim memory, then execute it on the victim machine.1
Uses AutoIt scripts dropped to a hidden directory during initial installation phases, such as test.au3.1
Was developed using the AutoIT scripting language.1
Has been distributed through an AutoIt loader script.1
All 5 software entries for this technique
Offense vs defense T1059.010
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
AutoHotKey & AutoIT detection strategy DET0332
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for AutoHotKey & AutoIT Abuse
AN0942 · Windows
Detects execution of AutoHotKey or AutoIT interpreters or compiled scripts used for unauthorized automation, command execution, or payload delivery, correlated with anomalous process lineage, command-line arguments, or script creation events.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TimeWindow | Tuning this helps identify automation behavior outside expected user work hours. |
| ParentProcessName | Used to isolate cases where AHK or AutoIT scripts are spawned by suspicious or unusual processes. |
| ScriptExtension | Extensions such as .ahk, .au3, or unknown .exe names compiled from these. |
| ChildProcessCount | Threshold for number of spawned children to detect automation or modular malware behavior. |
Use application control to prevent execution of AutoIt3.exe, AutoHotkey.exe, and other related features that may not be required for a given system or network to prevent potential misuse by adversaries.
Tests from Atomic Red Team (MIT licence) · technique definition