VirTool_Win32_Obfuscator_AAR

YARA detection rule by roadwy

VirTool:Win32/Obfuscator.AAR,SIGNATURE_TYPE_PEHSTR_EXT,0a 00 02 00 03 00 00

rule VirTool_Win32_Obfuscator_AAR{
	meta:
		description = "VirTool:Win32/Obfuscator.AAR,SIGNATURE_TYPE_PEHSTR_EXT,0a 00 02 00 03 00 00 "
		
	strings :
		$a_01_0 = {c7 45 e8 10 12 72 8e c7 45 f8 00 00 00 00 c7 45 f4 00 00 00 00 8b 45 10 89 45 f0 66 81 65 fc 6f c9 c6 45 e7 00 83 7d 0c 00 74 06 83 7d 08 00 75 02 } 		$a_01_1 = {eb 49 eb 09 8b 45 e7 03 45 ef 89 45 e7 8b 45 e7 3b 45 f7 73 33 81 6d eb 22 5f e4 e8 8b 45 0c } 		$a_01_2 = {83 7d 14 00 75 08 83 c8 ff e9 ed 00 00 00 8b 4d 14 8b 01 89 45 f4 81 45 e0 42 c2 1e 87 83 7d 10 00 75 5a } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1) >=2
 
}

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

717aa87e-9690-4a5c-813a-7c7c72587468

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