DarkGate AutoIt Execution from Suspicious User Path

SIGMA detection rule by Dragon Threat Intelligence · Unknown

Detects execution of legitimate or renamed AutoIt interpreters from user-writable directories, characteristic of DarkGate multi-stage loader payloads.

title: DarkGate AutoIt Execution from Suspicious User Path
id: b293c485-8672-4bfc-de12-039485762130
status: experimental
description: Detects execution of legitimate or renamed AutoIt interpreters from user-writable directories, characteristic of DarkGate multi-stage loader payloads.
references:
    - https://malpedia.caad.fkie.fraunhofer.de/details/win.darkgate
author: Dragon Threat Intelligence
date: 2026/03/24
tags:
    - attack.execution
    - attack.t1059
    - attack.defense_evasion
    - attack.t1036.005
logsource:
    category: process_creation
    product: windows
detection:
    selection_image:
        Image|endswith:
            - '\autoit3.exe'
            - '\autoit.exe'
            - '\autoit3_x64.exe'
    selection_desc:
        OriginalFileName: 'AutoIt3.exe'
    selection_path:
        CommandLine|contains:
            - '\AppData\Local\Temp\'
            - '\AppData\Roaming\'
            - '\ProgramData\'
            - 'C:\Users\Public\'
    condition: (selection_image or selection_desc) and selection_path
falsepositives:
    - Custom developer or sysadmin automation scripts running AutoIt in user directories
level: high

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

60fc74dd-46d5-41de-9cb8-d4299d6a4756

Propose edits, view related rules, and engage with the community through comments.

Executable code, not a declarative rule

This submission is arbitrary [[ currentRule.format ? currentRule.format.toUpperCase() : '' ]] code, not a declarative detection rule — review it as you would any script before running it, and note that it cannot be safely aggregated or auto-executed alongside YARA/Sigma/Suricata/CRS rules.

Rejected pattern present

[[ reason ]]

What does this mean?

Format & documentation suggestions

Not a security issue — this rule is valid and was accepted as-is. These are optional fields/conventions its own format recommends, mainly affecting its quality score and how well it documents itself for other reviewers.

[[ reason ]]

What do these messages mean?

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

[[ currentRule.title ]]

Community Discussion