Exploit_Linux_Enoket_A_MTB

YARA detection rule by roadwy

Exploit:Linux/Enoket.A!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,02 00 02 00 06 00 00

rule Exploit_Linux_Enoket_A_MTB{
	meta:
		description = "Exploit:Linux/Enoket.A!MTB,SIGNATURE_TYPE_ELFHSTR_EXT,02 00 02 00 06 00 00 "
		
	strings :
		$a_00_0 = {65 78 70 6c 6f 69 74 2e 63 } 		$a_00_1 = {2f 62 6f 6f 74 2f 53 79 73 74 65 6d 2e 6d 61 70 2d 25 73 } 		$a_00_2 = {47 6f 74 20 72 69 6e 67 30 } 		$a_00_3 = {46 61 69 6c 65 64 20 74 6f 20 65 78 65 63 20 72 6f 6f 74 73 68 65 6c 6c } 		$a_00_4 = {6b 61 6c 6c 73 79 6d 73 5f 69 73 5f 68 69 64 64 65 6e } 		$a_00_5 = {53 4d 45 50 20 64 65 74 65 63 74 65 64 2c 20 74 68 69 73 20 65 78 70 6c 6f 69 74 20 77 69 6c 6c 20 76 65 72 79 20 6c 69 6b 65 6c 79 20 66 61 69 6c 20 6f 6e 20 72 65 63 65 6e 74 20 6b 65 72 6e 65 6c 73 } 	condition:
		((#a_00_0  & 1)*1+(#a_00_1  & 1)*1+(#a_00_2  & 1)*1+(#a_00_3  & 1)*1+(#a_00_4  & 1)*1+(#a_00_5  & 1)*1) >=2
 
}

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

3e00b4d8-b4b2-48e4-99ab-350ba309e986

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