SUSP_Obfuscated_Powershell_decimal_b64

YARA detection rule by Greg Lesnewich · GPL-2.0

look for obfsucated powershell strings obfuscated via decimal_b64

rule SUSP_Obfuscated_Powershell_decimal_b64 {
  meta:
    author      = "Greg Lesnewich"
    description = "look for obfsucated powershell strings obfuscated via decimal_b64"
    date        = "2024-01-31"
    version     = "1.0"
    DaysOfYara  = "32/100"

  strings:
    $powershell_decimal_b64 = "112 111 119 101 114 115 104 101 108 108" base64 base64wide
    $PowerShell_decimal_b64 = "80 111 119 101 114 83 104 101 108 108" base64 base64wide
    $Powershell_decimal_b64 = "80 111 119 101 114 115 104 101 108 108" base64 base64wide

  condition:
    any of them
}

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

2f1a86e5-b2a2-414a-ac7e-4f374b9aa88b

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