HackTool_Win64_ArdentSeat_A_dha

YARA detection rule by roadwy

HackTool:Win64/ArdentSeat.A!dha,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00

rule HackTool_Win64_ArdentSeat_A_dha{
	meta:
		description = "HackTool:Win64/ArdentSeat.A!dha,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00 "
		
	strings :
		$a_01_0 = {78 2e 65 78 65 20 78 2e 78 2e 78 2e 78 3a 70 6f 72 74 } 		$a_01_1 = {6d 61 69 6e 2e 64 66 61 64 66 61 66 64 61 73 00 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1) >=2
 
}

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

b79dceee-092b-4870-ac46-b8c874e5d90f

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