Trojan_Win64_ClipBanker_AC_MTB_2

YARA detection rule by roadwy

Trojan:Win64/ClipBanker.AC!MTB,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00

rule Trojan_Win64_ClipBanker_AC_MTB_2{
	meta:
		description = "Trojan:Win64/ClipBanker.AC!MTB,SIGNATURE_TYPE_PEHSTR_EXT,05 00 05 00 05 00 00 "
		
	strings :
		$a_01_0 = {47 6f 20 62 75 69 6c 64 20 49 44 3a } 		$a_01_1 = {45 48 30 7a 53 56 6e 65 5a 50 53 75 46 52 31 31 42 6c 52 39 59 70 70 51 54 56 44 62 68 35 2b 31 36 41 6d 63 4a 69 34 67 31 7a 34 3d } 		$a_01_2 = {47 65 74 43 6c 69 70 62 6f 61 72 64 44 61 74 61 } 		$a_01_3 = {53 65 74 43 6c 69 70 62 6f 61 72 64 44 61 74 61 } 		$a_01_4 = {55 37 48 56 65 77 68 46 67 41 55 37 4d 50 53 44 39 45 71 4c 39 36 34 31 55 62 41 76 79 68 55 45 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1) >=5
 
}

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

c33a3627-7ce6-4f8a-92e7-a650fddbfaff

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