HackTool_Linux_ReverseSSH_C_MTB

YARA detection rule by roadwy

HackTool:Linux/ReverseSSH.C!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,04 00 04 00 04 00 00

rule HackTool_Linux_ReverseSSH_C_MTB{
	meta:
		description = "HackTool:Linux/ReverseSSH.C!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,04 00 04 00 04 00 00 "
		
	strings :
		$a_01_0 = {6d 61 69 6e 2e 52 75 6e } 		$a_01_1 = {6d 61 69 6e 2e 46 6f 72 6b } 		$a_01_2 = {72 65 76 65 72 73 65 5f 73 73 68 } 		$a_01_3 = {63 6c 69 65 6e 74 2f 68 61 6e 64 6c 65 72 73 2e 4c 6f 63 61 6c 46 6f 72 77 61 72 64 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1) >=4
 
}

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

e0ea9d77-341c-490a-9072-97fd41617f45

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