Backdoor_Win32_Teevsock_H

YARA detection rule by roadwy

Backdoor:Win32/Teevsock.H,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00

rule Backdoor_Win32_Teevsock_H{
	meta:
		description = "Backdoor:Win32/Teevsock.H,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00 "
		
	strings :
		$a_00_0 = {73 71 6c 73 72 76 2e 65 78 65 } 		$a_03_1 = {89 08 89 50 04 8d 84 ?? ?? ?? 00 00 8b f0 8a 08 83 c0 01 84 c9 75 f7 8d bc ?? ?? ?? 00 00 2b c6 83 c7 ff 8d a4 24 00 00 00 00 8a 4f 01 } 		$a_03_2 = {68 60 ea 00 00 ff 15 ?? ?? ?? 00 33 c9 33 c0 8a d1 80 c2 0d 30 90 90 ?? ?? ?? 00 83 f9 03 7e 04 33 c9 eb 03 } 	condition:
		((#a_00_0  & 1)*1+(#a_03_1  & 1)*1+(#a_03_2  & 1)*1) >=3
 
}

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

f434aa7e-2105-4ccb-a16c-28bab21019b1

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