VirTool_Win32_CeeInject_TO_bit_2

YARA detection rule by roadwy

VirTool:Win32/CeeInject.TO!bit,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00

rule VirTool_Win32_CeeInject_TO_bit_2{
	meta:
		description = "VirTool:Win32/CeeInject.TO!bit,SIGNATURE_TYPE_PEHSTR_EXT,04 00 04 00 04 00 00 "
		
	strings :
		$a_01_0 = {8a 0c 28 f6 d1 30 0c 18 40 3b c6 72 f3 } 		$a_03_1 = {8b ce 2b c8 51 03 c3 50 ff 93 ?? ?? ?? ?? 01 44 24 ?? 59 59 39 74 24 ?? 72 } 		$a_03_2 = {33 c0 81 34 83 ?? ?? ?? ?? 40 83 f8 10 72 f3 } 		$a_03_3 = {50 53 8b c6 e8 ?? ?? ?? ?? 59 59 33 c9 8a 14 0b 8b 44 24 0c 30 14 38 } 	condition:
		((#a_01_0  & 1)*1+(#a_03_1  & 1)*1+(#a_03_2  & 1)*1+(#a_03_3  & 1)*1) >=4
 
}

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

e5dfc0cf-ddfb-43fb-9e52-7b80cd4534b2

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