VirTool_BAT_Obfuscator_AS

YARA detection rule by roadwy

VirTool:BAT/Obfuscator.AS,SIGNATURE_TYPE_PEHSTR_EXT,64 00 01 00 01 00 00

rule VirTool_BAT_Obfuscator_AS{
	meta:
		description = "VirTool:BAT/Obfuscator.AS,SIGNATURE_TYPE_PEHSTR_EXT,64 00 01 00 01 00 00 "
		
	strings :
		$a_01_0 = {50 71 70 4b 51 51 62 53 47 46 61 6c 73 65 50 71 70 4b 51 51 62 53 47 50 71 70 4b 51 51 62 53 47 46 61 6c 73 65 50 71 70 4b 51 51 62 53 47 } 	condition:
		((#a_01_0  & 1)*1) >=1
 
}

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

bef8f80e-f222-4f9e-91b7-5ae5ce13e05c

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