Ransom_MSIL_MosnCrypt_MK_MTB

YARA detection rule by roadwy

Ransom:MSIL/MosnCrypt.MK!MTB,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00

rule Ransom_MSIL_MosnCrypt_MK_MTB{
	meta:
		description = "Ransom:MSIL/MosnCrypt.MK!MTB,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00 "
		
	strings :
		$a_80_0 = {49 4e 46 4f 52 4d 41 54 49 4f 4e 5f 52 45 41 44 5f 4d 45 2e 74 78 74 } 		$a_80_1 = {46 49 4c 45 53 2d 45 4e 43 52 59 50 54 45 44 3a } 		$a_80_2 = {48 41 52 44 57 41 52 45 2d 49 44 5f 49 4e 43 4c 55 44 45 5f 49 4e 5f 4d 41 49 4c 3a } 		$a_80_3 = {45 4e 43 52 59 50 54 45 44 5f 4d 45 4d 4f 52 59 5f 53 54 52 49 4e 47 53 } 		$a_80_4 = {45 6e 63 72 79 70 74 41 6c 6c 46 69 6c 65 73 } 	condition:
		((#a_80_0  & 1)*1+(#a_80_1  & 1)*1+(#a_80_2  & 1)*1+(#a_80_3  & 1)*1+(#a_80_4  & 1)*1) >=5
 
}

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

22f779b9-afbe-48d7-871a-3e12b2658f83

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