Ransom_Win32_Ruyk_A_ibt

YARA detection rule by roadwy

Ransom:Win32/Ruyk.A!ibt,SIGNATURE_TYPE_PEHSTR,02 00 02 00 02 00 00

rule Ransom_Win32_Ruyk_A_ibt{
	meta:
		description = "Ransom:Win32/Ruyk.A!ibt,SIGNATURE_TYPE_PEHSTR,02 00 02 00 02 00 00 "
		
	strings :
		$a_01_0 = {83 7d f4 08 7d 28 8b 45 fc 83 e0 01 74 10 8b 4d fc d1 e9 81 f1 20 83 b8 ed 89 4d f0 eb 08 8b 55 fc d1 ea 89 55 f0 } 		$a_01_1 = {8b 45 0c 89 45 ec 8b 4d 0c 83 e9 01 89 4d 0c 83 7d ec 00 74 29 8b 55 08 0f b6 02 33 45 fc 25 ff 00 00 00 8b 4d fc c1 e9 08 33 8c 85 ec fb ff ff 89 4d fc 8b 55 08 83 c2 01 89 55 08 eb c2 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1) >=2
 
}

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

5c343e43-e5a2-40ad-b78b-182e3c4f17fa

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