Backdoor_Win32_Zegost_G

YARA detection rule by roadwy

Backdoor:Win32/Zegost.G,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 04 00 00

rule Backdoor_Win32_Zegost_G{
	meta:
		description = "Backdoor:Win32/Zegost.G,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 04 00 00 "
		
	strings :
		$a_03_0 = {8a 14 01 80 f2 ?? 88 10 40 ?? 75 f4 } 		$a_03_1 = {3d 00 00 20 03 73 0d 6a 02 56 56 ff 75 ?? ff 15 } 		$a_02_2 = {88 9e b5 00 00 00 c6 45 ?? 48 c6 45 ?? 65 c6 45 ?? 61 c6 45 ?? 72 c6 45 ?? 74 } 		$a_00_3 = {5c 73 79 73 6c 6f 67 2e 64 61 74 00 25 64 2e 62 61 6b 00 } 	condition:
		((#a_03_0  & 1)*1+(#a_03_1  & 1)*1+(#a_02_2  & 1)*1+(#a_00_3  & 1)*1) >=3
 
}

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

47aecee3-73a5-4c1c-b4af-ed3f47f1e036

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