Trojan_Win32_Sfloost_A_bit

YARA detection rule by roadwy

Trojan:Win32/Sfloost.A!bit,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00

rule Trojan_Win32_Sfloost_A_bit{
	meta:
		description = "Trojan:Win32/Sfloost.A!bit,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00 "
		
	strings :
		$a_03_0 = {8a 1e 2a d1 02 d3 80 ea ?? 46 88 ?? ?? ?? ?? ?? 40 4f 75 e6 } 		$a_01_1 = {49 70 74 61 62 4c 65 78 20 53 65 72 76 69 63 65 73 } 		$a_01_2 = {47 6c 6f 62 61 6c 5c 68 62 6c 6c 78 78 78 78 53 65 72 76 65 72 } 		$a_01_3 = {47 6c 6f 62 61 6c 5c 68 62 6c 6c 78 78 78 78 43 6c 69 65 6e 74 } 	condition:
		((#a_03_0  & 1)*2+(#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 ]]

4eafaccf-26ce-4d60-a6f2-8f5eff821b37

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