INDICATOR_TOOL_Havoc

YARA detection rule by ditekSHen · NOASSERTION

Detects Havoc Demon

import "pe"
rule INDICATOR_TOOL_Havoc {
    meta:
        author = "ditekSHen"
        description = "Detects Havoc Demon"
    strings:
        $x1 = "X-Havoc:" wide
        $x2 = "X-Havoc-Agent:" wide
        $s1 = "\\Werfault.exe" wide
        $s2 = "/funny_cat.gif" wide
    condition:
        uint16(0) == 0x5a4d and (all of ($x*) or 3 of them or
            (
                pe.number_of_imports == 0 and 
                pe.number_of_exports == 0 and 
                2 of them
            ) 
        )
}

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

a61b8aed-a83c-43ee-aa00-5f7c541ef37a

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