Ransom_Win32_MedusaLocker_AA_MTB

YARA detection rule by roadwy

Ransom:Win32/MedusaLocker.AA!MTB,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00

rule Ransom_Win32_MedusaLocker_AA_MTB{
	meta:
		description = "Ransom:Win32/MedusaLocker.AA!MTB,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00 "
		
	strings :
		$a_01_0 = {4d 65 64 75 73 61 5c 52 65 6c 65 61 73 65 5c 67 61 7a 65 2e 70 64 62 } 		$a_01_1 = {57 65 20 68 61 76 65 20 50 45 4e 45 54 52 41 54 45 20 79 6f 75 72 20 6e 65 74 77 6f 72 6b 20 61 6e 64 20 43 4f 50 49 45 44 20 64 61 74 61 } 		$a_01_2 = {57 65 20 68 61 76 65 20 45 4e 43 52 59 50 54 45 44 20 73 6f 6d 65 20 79 6f 75 72 20 66 69 6c 65 73 } 		$a_01_3 = {4d 45 44 55 53 41 20 44 45 43 52 59 50 54 4f 52 20 61 6e 64 20 44 45 43 52 59 50 54 49 4f 4e 20 4b 45 59 73 } 	condition:
		((#a_01_0  & 1)*1+(#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 ]]

6335bc72-22d9-470e-acb3-0b86fe642c1a

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