Backdoor_Linux_Bifrose_B_MTB

YARA detection rule by roadwy

Backdoor:Linux/Bifrose.B!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,05 00 05 00 02 00 00

rule Backdoor_Linux_Bifrose_B_MTB{
	meta:
		description = "Backdoor:Linux/Bifrose.B!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,05 00 05 00 02 00 00 "
		
	strings :
		$a_02_0 = {c7 45 c4 ff ff ff ff 83 ec 0c 68 ?? ?? ?? 08 e8 ?? ?? ?? ?? 83 c4 10 83 ec 04 6a 06 6a 01 6a 02 e8 ?? ?? ?? ?? 83 c4 10 89 45 c4 83 7d c4 00 79 12 83 ec 0c 6a 0a e8 ?? ?? ?? ?? 83 c4 10 e9 } 		$a_02_1 = {48 63 05 56 55 20 00 48 6b c0 3e 4a 8d 14 28 41 0f bf 4c 05 3c bf b8 5d 40 00 31 c0 e8 ?? ?? ?? ?? bf c4 5d 40 00 31 c0 e8 ?? ?? ?? ?? bf 02 00 00 00 be 01 00 00 00 ba 06 00 00 00 e8 ?? ?? ?? ?? 41 89 c4 45 85 e4 } 	condition:
		((#a_02_0  & 1)*5+(#a_02_1  & 1)*5) >=5
 
}

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

e76c8c3f-ca01-429b-a86a-acdbba00bba3

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