Backdoor_Linux_Shellshock_A

YARA detection rule by roadwy

Backdoor:Linux/Shellshock.A,SIGNATURE_TYPE_ELFHSTR_EXT,03 00 02 00 03 00 00

rule Backdoor_Linux_Shellshock_A{
	meta:
		description = "Backdoor:Linux/Shellshock.A,SIGNATURE_TYPE_ELFHSTR_EXT,03 00 02 00 03 00 00 "
		
	strings :
		$a_00_0 = {4a 55 4e 4b 20 46 6c 6f 6f 64 69 6e 67 20 25 73 3a 25 64 20 66 6f 72 20 25 64 20 73 65 63 6f 6e 64 73 2e 00 } 		$a_00_1 = {2f 62 69 6e 2f 62 75 73 79 62 6f 78 3b 65 63 68 6f 20 2d 65 20 27 5c 31 34 37 5c 31 34 31 5c 31 37 31 5c 31 34 36 5c 31 34 37 5c 31 36 34 27 } 		$a_00_2 = {67 61 79 66 67 74 00 } 	condition:
		((#a_00_0  & 1)*1+(#a_00_1  & 1)*1+(#a_00_2  & 1)*1) >=2
 
}

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

51b5f6ed-ca04-474c-a3f5-b71f6a4b13e0

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