Process Execution sans Command Lines

SIGMA detection rule by Micah Babinski · GPL-3.0

Looks for process execution with no command line arguments, which may indicate process injection. Inspired by the 2022 Red Canary Threat Detection report.

title: Process Execution sans Command Lines
id: e0a2f82f-d11d-4ea7-af7e-a8f760b07c04
status: experimental
description: Looks for process execution with no command line arguments, which may
    indicate process injection. Inspired by the 2022 Red Canary Threat Detection report.
references:
    - https://redcanary.com/threat-detection-report/techniques/process-injection/
author: Micah Babinski
date: 2022/11/03
tags:
    - attack.privilege_escalation
    - attack.t1055
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\backgroundtaskhost.exe'
            - '\svchost.exe'
            - '\dllhost.exe'
            - '\werfault.exe'
            - '\searchprotocolhost.exe'
            - '\wuauclt.exe'
            - '\spoolsv.exe'
            - '\rundll32.exe'
            - '\regasm.exe'
            - '\regsvr32.exe'
            - '\regsvcs.exe'
        # looks for command line values ending with exe or exe" and no other characters following
        CommandLine|re: '^.*\.exe(\s|")*$'
    condition: selection
falsepositives:
    - Unknown
level: high

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

50fe5930-04cd-430d-b382-23afcc165f99

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