INDICATOR_KB_ID_Ransomware_Thanos

YARA detection rule by ditekShen · NOASSERTION

Detects files referencing identities associated with Thanos ransomware

rule INDICATOR_KB_ID_Ransomware_Thanos {
    meta:
        author = "ditekShen"
        description = "Detects files referencing identities associated with Thanos ransomware"
    strings:
        $s1 = "my-contact-email@protonmail.com" ascii wide nocase
        $s2 = "get-my-data@protonmail.com" ascii wide nocase
    condition:
        any of them
}

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

36284fd2-ac26-4ec1-a69f-c1c5ede98b1d

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