Ransom_Win32_Sondin_P_MSR

YARA detection rule by roadwy

Ransom:Win32/Sondin.P!MSR,SIGNATURE_TYPE_PEHSTR,04 00 04 00 06 00 00

rule Ransom_Win32_Sondin_P_MSR{
	meta:
		description = "Ransom:Win32/Sondin.P!MSR,SIGNATURE_TYPE_PEHSTR,04 00 04 00 06 00 00 "
		
	strings :
		$a_01_0 = {6e 6e 61 6d 65 22 3a 22 7b 45 58 54 7d 2d 72 65 61 64 6d 65 2e 74 78 74 22 } 		$a_01_1 = {64 62 67 22 3a 66 61 6c 73 65 } 		$a_01_2 = {66 61 73 74 22 3a 66 61 6c 73 65 } 		$a_01_3 = {77 69 70 65 22 3a 66 61 6c 73 65 } 		$a_01_4 = {77 68 74 22 3a 7b 22 66 6c 64 22 3a 5b } 		$a_01_5 = {6a 61 78 2d 69 6e 74 65 72 69 6d 2d 61 6e 64 2d 70 72 6f 6a 65 63 74 6d 61 6e 61 67 65 6d 65 6e 74 2e 63 6f 6d } 	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+(#a_01_5  & 1)*1) >=4
 
}

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

f778d968-4dc0-4f76-9b6e-bc5e2c655fcf

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