plugx_decrypt

YARA detection rule by @h3x2b <tracker _AT h3x.eu>

Detect constants used in the plugx decrypt function

rule plugx_decrypt : APT
{
    meta:
        description = "Detect constants used in the plugx decrypt function"
	author = "@h3x2b <tracker _AT h3x.eu>"
                                                                                                                        
    strings:
        $yes_v1 = { 31 F5 CD 1A }
        $yes_v2 = { F2 DC AF 2C }
        $yes_v3 = { 93 23 71 34 }
        $yes_v4 = { A4 C7 AD 46 }

    condition:
                uint16(0) == 0x5a4d

        and all of ( $yes_* )
}

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

4c3a5d85-e4ad-4b72-ac53-79c0597fd387

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