VirTool_Win32_Obfuscator_IN

YARA detection rule by roadwy

VirTool:Win32/Obfuscator.IN,SIGNATURE_TYPE_PEHSTR_EXT,0a 00 01 00 01 00 00

rule VirTool_Win32_Obfuscator_IN{
	meta:
		description = "VirTool:Win32/Obfuscator.IN,SIGNATURE_TYPE_PEHSTR_EXT,0a 00 01 00 01 00 00 "
		
	strings :
		$a_01_0 = {8d 34 08 8b 34 b3 2b 74 82 10 33 34 82 56 8d 34 08 8b 7d fc 8d 3c b7 5e 89 37 8b 74 82 20 01 34 82 8b 74 82 30 01 74 82 10 40 83 f8 04 72 d1 83 c1 04 3b 4d 10 } 	condition:
		((#a_01_0  & 1)*1) >=1
 
}

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

92f949e3-349a-4d52-abed-2662b4e5e84c

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