Backdoor_Win32_Zegost_ME

YARA detection rule by roadwy

Backdoor:Win32/Zegost.ME,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00

rule Backdoor_Win32_Zegost_ME{
	meta:
		description = "Backdoor:Win32/Zegost.ME,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00 "
		
	strings :
		$a_01_0 = {81 c3 58 9e 00 00 6a 01 53 ff d5 5f 5e 5d 5b c2 08 00 } 		$a_01_1 = {42 45 49 5a 48 55 } 		$a_01_2 = {43 3a 5c 31 2e 74 6d 70 } 		$a_01_3 = {5b 42 41 43 4b 53 50 41 43 45 5d } 		$a_01_4 = {5b 50 72 69 6e 74 20 53 63 72 65 65 6e 5d } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1) >=5
 
}

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

005f5b3c-4fc2-4112-81e3-1d8a90add327

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