Backdoor_Win32_Hupigon_DG

YARA detection rule by roadwy

Backdoor:Win32/Hupigon.DG,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00

rule Backdoor_Win32_Hupigon_DG{
	meta:
		description = "Backdoor:Win32/Hupigon.DG,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00 "
		
	strings :
		$a_01_0 = {43 6d 64 30 30 31 00 00 ff ff ff ff 06 00 00 00 43 6d 64 30 30 32 00 } 		$a_00_1 = {4b 45 52 4e 45 4c 33 32 2e 44 4c 4c 00 00 00 00 52 65 67 69 73 74 65 72 53 65 72 76 69 63 65 50 72 6f 63 65 73 73 00 } 		$a_03_2 = {8b f0 89 35 ?? ?? ?? ?? 85 f6 74 0e 6a 01 e8 ?? ?? ?? ?? 50 ff 15 ?? ?? ?? ?? 53 e8 ?? ?? ?? ?? 33 c0 } 	condition:
		((#a_01_0  & 1)*1+(#a_00_1  & 1)*1+(#a_03_2  & 1)*1) >=3
 
}

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

e198c36b-3675-4995-8b0b-5dd42b258636

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