DoS_Win32_CaddyWiper_F_dha

YARA detection rule by roadwy

DoS:Win32/CaddyWiper.F!dha,SIGNATURE_TYPE_PEHSTR_EXT,64 00 64 00 01 00 00

rule DoS_Win32_CaddyWiper_F_dha{
	meta:
		description = "DoS:Win32/CaddyWiper.F!dha,SIGNATURE_TYPE_PEHSTR_EXT,64 00 64 00 01 00 00 "
		
	strings :
		$a_43_0 = {5c 24 50 90 01 01 89 5c 24 38 90 01 01 89 5c 24 58 48 90 01 04 89 5c 24 60 41 b9 80 07 00 00 48 90 01 04 4d 8b c4 ba 54 c0 07 00 49 8b cd 90 00 00 } 	condition:
		((#a_43_0  & 1)*100) >=100
 
}

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

41f1a789-69f1-4c70-8d6c-4d85b56debac

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