VirTool_Win32_Obfuscator_RR

YARA detection rule by roadwy

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

rule VirTool_Win32_Obfuscator_RR{
	meta:
		description = "VirTool:Win32/Obfuscator.RR,SIGNATURE_TYPE_PEHSTR_EXT,0a 00 01 00 01 00 00 "
		
	strings :
		$a_03_0 = {89 50 2e 89 48 39 8d 90 90 a7 02 00 00 8d 88 b6 02 00 00 89 50 44 89 48 4f c6 40 60 bf 8b 15 ?? ?? ?? ?? 89 50 61 c6 40 65 90 90 } 	condition:
		((#a_03_0  & 1)*1) >=1
 
}

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

1db8cdfe-efcc-4033-bc56-d95025f11584

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