MTI_Hunting_AsRockDriver_Exploit_Generic

YARA detection rule by Mandiant

Searching for executables containing strings associated with AsRock driver Exploit.

rule MTI_Hunting_AsRockDriver_Exploit_Generic : hardened
{
	meta:
		author = "Mandiant"
		date = "03-23-2022"
		description = "Searching for executables containing strings associated with AsRock driver Exploit."
		score = 40

	strings:
		$dos_stub = {54 68 69 73 20 70 72 6f 67 72 61 6d 20 63 61 6e 6e 6f 74 20 62 65 20 72 75 6e 20 69 6e 20 44 4f 53 20 6d 6f 64 65}
		$pdb_good = {63 3a 5c 61 73 72 6f 63 6b 5c 77 6f 72 6b 5c 61 73 72 6f 63 6b 73 64 6b 5f 76 30 2e 30 2e 36 39 5c 61 73 72 72 77 5c 73 72 63 5c 64 72 69 76 65 72 5c 73 72 63 5c 6f 62 6a 66 72 65 5f 77 69 6e 37 5f 61 6d 64 36 34 5c 61 6d 64 36 34 5c 41 73 72 44 72 76 31 30 33 2e 70 64 62}

	condition:
		all of them and ( #dos_stub == 2 ) and ( @pdb_good > @dos_stub [ 2 ] )
}

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

fa21a704-5678-4919-b73d-9e7fde2476a1

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