VirTool_Win32_CeeInject_ABB_bit

YARA detection rule by roadwy

VirTool:Win32/CeeInject.ABB!bit,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00

rule VirTool_Win32_CeeInject_ABB_bit{
	meta:
		description = "VirTool:Win32/CeeInject.ABB!bit,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00 "
		
	strings :
		$a_03_0 = {8b c6 33 d2 52 50 8b c3 99 03 04 24 13 54 24 04 83 c4 08 8a 91 ?? ?? ?? ?? 80 f2 ba 88 10 41 } 		$a_03_1 = {5f 5e 5b c3 90 0a 70 00 6a 00 68 ?? ?? ?? ?? e8 ?? ?? ?? ?? 90 05 10 01 90 83 fb ?? 90 05 10 01 90 7e ?? 90 05 10 01 90 c7 05 ?? ?? ?? ?? ?? ?? ?? ?? 90 05 10 01 90 [0-02] e8 ?? ?? ?? ?? 90 05 10 01 90 eb ?? 90 05 10 01 90 4e 75 ?? 90 05 10 01 90 5f 5e 5b c3 } 	condition:
		((#a_03_0  & 1)*1+(#a_03_1  & 1)*1) >=2
 
}

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

8889362c-d729-4312-8317-7b49da555889

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