Autoit
Table of Contents
Overview
AutoIt (classified across commercial antivirus vendors as Trojan:Win32/AutoIt, Packer:Win32/AutoIt, and Backdoor.AutoIt) is a widely abused legitimate freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting tasks. Because AutoIt provides native capabilities to compile scripts into standalone portable executable (PE) binaries containing an embedded interpreter and compressed script resources, cybercriminal actors and malware authors extensively leverage it to package trojans, info-stealers (like Agent Tesla, FormBook, and Lokibot), and keyloggers. AutoIt compiled executables disguise underlying malicious shellcode inside heavily obfuscated, multi-thousand-line decoy script strings. Upon execution, the compiled AutoIt interpreter dynamically deobfuscates the embedded payload, decrypts binary arrays, and injects the unpacked payload into legitimate Windows host processes like RegSvcs.exe, MSBuild.exe, or svchost.exe using process hollowing techniques.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Autoit_Compiled_Scripting_Framework
Known Derivatives & Downstream Variants: Autoit.Loader · Trojan.Autoit.Gen · Packer.Autoit
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.007: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-EDA | Executable Deobfuscation Analysis | Detect | T1027.002 | Deploy static entropy scanners and dynamic memory-unpacking heuristics to identify obfuscated and packed PE structures. |
D3-PHA | Process Hollowing Analysis | Detect | T1055.012 | Inspect unbacked executable memory regions (PAGE_EXECUTE_READWRITE) for replaced PE image headers inside legitimate host processes. |
D3-SEA | Script Execution Analysis | Detect | T1059.007 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
D3-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
a1b0c9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0b0c9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0c9
Delivery vectors
Phishing emails with malicious zip archives containing compiled .exe AutoIt stagersCompromised software distribution portals hosting trojanized setup packages
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\AutoItScriptLauncherStartup folder shortcut: '%AppData%\Microsoft\Windows\Start Menu\Programs\Startup\script.a3x.lnk'
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_AUTOIT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Autoit"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "autoit" ascii wide nocase
$s2 = "trojan:win32/autoit" ascii wide nocase
$s3 = "packer:win32/autoit" ascii wide nocase
$s4 = "backdoor.autoit" ascii wide nocase
$s5 = "win32/autoit.packer" ascii wide nocase
$s6 = "autoit3.dropper" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Autoit (Packer) Execution & Triage
id: 6db2f3aa-103f-55b4-949a-3c76512c2270
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Autoit malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/autoit
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.packer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1027_002
- attack.t1059_007
- attack.t1055_012
- attack.t1547_001
- attack.t1112
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_AUTOIT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Autoit tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "autoit" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Terminate suspicious compiled AutoIt parent processes and any spawned hollowed child processes (e.g., RegSvcs.exe).
- Isolate the host from the network to halt ongoing C2 beaconing by dropped info-stealer modules.
- Inspect and remove rogue AutoIt script files dropped into %AppData% or %Temp%.
- Implement WDAC or AppLocker rules to prevent execution of unapproved compiled script binaries.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not whitelist AutoIt compiler executables globally across enterprise endpoints.
- Avoid treating AutoIt detections as simple scripting utilities; they almost universally conceal high-severity trojans.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Trojan:Win32/AutoIt Analysis
- Malwarebytes Labs Threat Intelligence - Backdoor.AutoIt Overview
- NIST National Vulnerability Database - CVE-2017-11882
- Search "autoit" on VirusTotal (External Analysis)
- Search "autoit" on Any.Run (Sandbox Sandbox)
- Search "autoit" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is the AutoIt malware classification?
AutoIt malware refers to compiled AutoIt scripts tracked by Microsoft Defender weaponized to pack and stealthily execute secondary trojans.
How do threat actors abuse AutoIt for defense evasion?
Attackers obfuscate malicious payloads inside encrypted script resources and use the legitimate interpreter engine to evade static antivirus detection.
What injection methods are used by AutoIt compiled droppers?
AutoIt loaders frequently use process hollowing to inject decrypted payloads into legitimate Windows binaries like RegSvcs.exe or svchost.exe.
Which CVE vulnerabilities have been associated with AutoIt delivery?
Campaigns delivering compiled AutoIt loaders have historically exploited Office vulnerabilities including CVE-2012-0158 and CVE-2017-11882.
How can security operations teams mitigate AutoIt loader threats?
Organizations should block unauthorized compiled AutoIt executables using application control policies, inspect memory for hollowed processes, and monitor EDR telemetry.
How do I remove Autoit from Windows?
Manual removal of Autoit is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Autoit infection?
Symptoms of Autoit can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Packers
Want to prevent Autoit and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/autoit.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.