Exploit_Win32_Shellcode_MM_MTB

YARA detection rule by roadwy

Exploit:Win32/Shellcode.MM!MTB,SIGNATURE_TYPE_PEHSTR,01 00 01 00 01 00 00

rule Exploit_Win32_Shellcode_MM_MTB{
	meta:
		description = "Exploit:Win32/Shellcode.MM!MTB,SIGNATURE_TYPE_PEHSTR,01 00 01 00 01 00 00 "
		
	strings :
		$a_01_0 = {33 c9 83 f8 29 0f 45 c8 8a 84 0c 80 00 00 00 30 84 14 b8 00 00 00 42 8d 41 01 81 fa 7d 08 00 00 72 de } 	condition:
		((#a_01_0  & 1)*1) >=1
 
}

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

e634e172-a350-4f8b-b0e8-d2916825304c

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