TrojanSpy_Win32_Banker_AOE

YARA detection rule by roadwy

TrojanSpy:Win32/Banker.AOE,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 05 00 00

rule TrojanSpy_Win32_Banker_AOE{
	meta:
		description = "TrojanSpy:Win32/Banker.AOE,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 05 00 00 "
		
	strings :
		$a_00_0 = {2e 70 6f 73 74 66 69 78 63 6f 6d 62 6f 2e 63 6f 6d } 		$a_01_1 = {39 35 39 36 36 44 38 45 39 32 36 36 41 39 42 42 38 41 44 35 36 37 43 36 38 37 43 41 38 45 } 		$a_01_2 = {33 36 46 45 30 44 31 43 46 31 30 35 31 41 32 39 45 46 30 36 30 41 } 		$a_01_3 = {31 43 45 32 33 33 43 32 39 31 36 44 42 38 34 38 } 		$a_01_4 = {eb 05 bf 01 00 00 00 8b 45 e4 33 db 8a 5c 38 ff 33 5d e0 3b 5d ec 7f 0b 81 c3 ff 00 00 00 2b 5d ec eb 03 } 	condition:
		((#a_00_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1) >=3
 
}

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

9dee30f6-c5f1-4100-834a-b7f6f7bd0f3c

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