Backdoor_Win32_Zegost_DE_bit

YARA detection rule by roadwy

Backdoor:Win32/Zegost.DE!bit,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00

rule Backdoor_Win32_Zegost_DE_bit{
	meta:
		description = "Backdoor:Win32/Zegost.DE!bit,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00 "
		
	strings :
		$a_03_0 = {ff 5c c6 85 ?? ?? ?? ?? 52 c6 85 ?? ?? ?? ?? 75 c6 85 ?? ?? ?? ?? 25 c6 85 ?? ?? ?? ?? 64 c6 85 ?? ?? ?? ?? 2e c6 85 ?? ?? ?? ?? 45 } 		$a_03_1 = {ff 50 c6 85 ?? ?? ?? ?? 6c c6 85 ?? ?? ?? ?? 75 c6 85 ?? ?? ?? ?? 67 c6 85 ?? ?? ?? ?? 69 c6 85 ?? ?? ?? ?? 6e c6 85 ?? ?? ?? ?? 33 c6 85 ?? ?? ?? ?? 32 c6 85 ?? ?? ?? ?? 2e c6 85 ?? ?? ?? ?? 64 } 	condition:
		((#a_03_0  & 1)*1+(#a_03_1  & 1)*1) >=2
 
}

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

94c06f73-5a70-4e33-b9ae-f5b271035a2f

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