Ransom_Win32_Genasom_AJ

YARA detection rule by roadwy

Ransom:Win32/Genasom.AJ,SIGNATURE_TYPE_PEHSTR,05 00 05 00 05 00 00

rule Ransom_Win32_Genasom_AJ{
	meta:
		description = "Ransom:Win32/Genasom.AJ,SIGNATURE_TYPE_PEHSTR,05 00 05 00 05 00 00 "
		
	strings :
		$a_01_0 = {00 66 69 72 65 66 6f 78 2e 65 78 65 22 } 		$a_01_1 = {00 6f 70 65 72 61 2e 65 78 65 22 } 		$a_01_2 = {72 65 67 20 61 64 64 20 22 48 4b 45 59 5f 43 55 52 52 45 4e 54 5f 55 53 45 52 5c 53 6f 66 74 77 61 72 65 5c 4d 69 63 72 6f 73 6f 66 74 5c 57 69 6e 64 6f 77 73 5c 43 75 72 72 65 6e 74 56 65 72 73 69 6f 6e 5c 72 75 6e 22 20 } 		$a_01_3 = {53 6f 66 74 77 61 72 65 5c 57 65 62 4d 6f 6e 65 79 5c 70 61 74 68 } 		$a_01_4 = {73 00 6d 00 73 00 2d 00 70 00 72 00 69 00 63 00 65 00 2e 00 72 00 75 00 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1) >=5
 
}

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

c56f392a-964b-49d9-87b9-0d9ed698a4f0

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