Backdoor_Win32_Zeprox_B

YARA detection rule by roadwy

Backdoor:Win32/Zeprox.B,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00

rule Backdoor_Win32_Zeprox_B{
	meta:
		description = "Backdoor:Win32/Zeprox.B,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00 "
		
	strings :
		$a_03_0 = {8b 00 8b f0 85 f6 7e 38 c7 45 ?? 01 00 00 00 8b 45 ?? 8b 55 ?? 0f b6 44 10 ff 83 e8 20 8b df 33 d8 83 c3 20 8d 45 ?? 8b d3 e8 ?? ?? ff ff 8b 55 ?? 8d 45 ?? e8 ?? ?? ff ff 47 ff 45 ?? 4e 75 cf } 		$a_01_1 = {53 76 63 32 64 6c 6c } 		$a_01_2 = {23 6a 6e 64 } 		$a_01_3 = {5c 41 70 70 6c 69 63 61 74 69 6f 6e 20 44 61 74 61 5c 4d 61 63 72 6f 6d 65 64 69 61 5c 46 6c 61 73 68 20 50 6c 61 79 65 72 5c 23 53 68 61 72 65 64 4f 62 6a 65 63 74 73 } 	condition:
		((#a_03_0  & 1)*2+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1) >=4
 
}

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

cb6b8fd5-a72a-4a10-be98-a08550e7c6a1

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