Trojan_Win64_Bumblebee_FS_MTB

YARA detection rule by roadwy

Trojan:Win64/Bumblebee.FS!MTB,SIGNATURE_TYPE_PEHSTR,01 00 01 00 01 00 00

rule Trojan_Win64_Bumblebee_FS_MTB{
	meta:
		description = "Trojan:Win64/Bumblebee.FS!MTB,SIGNATURE_TYPE_PEHSTR,01 00 01 00 01 00 00 "
		
	strings :
		$a_01_0 = {43 8a 0c 17 2a 8c 24 88 00 00 00 32 8c 24 80 00 00 00 49 8b 43 20 41 88 0c 02 } 	condition:
		((#a_01_0  & 1)*1) >=1
 
}

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

5eb23c64-fd18-46fd-b0a0-950773d797de

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