Sanesecurity_BlackEnergy

YARA detection rule by HydraDragonAntivirus · GPL-2.0

Rule Sanesecurity_BlackEnergy (No description metadata provided).

rule Sanesecurity_BlackEnergy {
  strings:
    $hc1 = { 68 97 04 81 1D 6A 01 }
    $hc2 = { 68 A8 06 B0 3B 6A 02 }
    $hc3 = { 68 14 06 F5 33 6A 01 }
    $hc4 = { 68 AF 02 91 AB 6A 01 }
    $hc5 = { 68 8A 86 39 56 6A 02 }
    $hc6 = { 68 19 2B 90 95 6A 01 }
    $hc7 = { (68 | B?) 11 05 90 23 }
    $hc8 = { (68 | B?) EB 05 4A 2F }
    $hc9 = { (68 | B?) B7 05 57 2A }

  condition:
    2 of ($hc*)
}

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

df37f590-a064-4efc-be2b-6d50d1a8ef9e

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