VirTool_Win32_Obfuscator_OO

YARA detection rule by roadwy

VirTool:Win32/Obfuscator.OO,SIGNATURE_TYPE_PEHSTR_EXT,64 00 01 00 01 00 00

rule VirTool_Win32_Obfuscator_OO{
	meta:
		description = "VirTool:Win32/Obfuscator.OO,SIGNATURE_TYPE_PEHSTR_EXT,64 00 01 00 01 00 00 "
		
	strings :
		$a_03_0 = {8a 0c 39 32 4c 02 ?? 8b 40 ?? 88 0c 07 8b 45 08 ff 40 ?? 8b 45 08 ff 80 ?? ?? 00 00 [0-02] 8b 45 08 83 78 ?? 04 72 ?? 89 ?? ?? eb } 	condition:
		((#a_03_0  & 1)*1) >=1
 
}

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

8b017e8f-df07-4edf-8a42-9db5cf07097f

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