Exploit_Win32_ShellCode_AE

YARA detection rule by roadwy

Exploit:Win32/ShellCode.AE,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 04 00 00

rule Exploit_Win32_ShellCode_AE{
	meta:
		description = "Exploit:Win32/ShellCode.AE,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 04 00 00 "
		
	strings :
		$a_01_0 = {c7 44 24 48 6b 65 72 6e c7 44 24 4c 65 6c 33 32 } 		$a_01_1 = {c6 45 c9 77 c6 45 ca 62 c6 45 cb 65 } 		$a_01_2 = {c6 45 a0 70 c6 45 a1 6f c6 45 a2 77 } 		$a_01_3 = {c7 45 f8 2e 65 78 65 c6 45 fc 00 8d 55 f8 84 c0 74 25 57 8b fa 8b f1 2b f7 5f 3c 2e } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1) >=3
 
}

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

646a2041-35dd-4ea4-973f-2cb6d9b99ed6

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