VirTool_Win32_CeeInject_TS_bit_2

YARA detection rule by roadwy

VirTool:Win32/CeeInject.TS!bit,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00

rule VirTool_Win32_CeeInject_TS_bit_2{
	meta:
		description = "VirTool:Win32/CeeInject.TS!bit,SIGNATURE_TYPE_PEHSTR_EXT,03 00 03 00 03 00 00 "
		
	strings :
		$a_03_0 = {33 c0 89 45 ?? 99 f7 7d ?? 8b 45 ?? 8a 8a ?? ?? ?? ?? 8b 55 ?? c0 e1 03 32 c8 88 0c 02 40 3b c7 89 45 } 		$a_03_1 = {8b c7 99 f7 7d ?? 8b 45 ?? 8a 04 02 30 04 3e 47 3b 7d ?? 7c eb } 		$a_03_2 = {8b c1 99 bf ?? ?? 00 00 f7 ff 8b 45 ?? 8a 04 02 30 04 31 41 81 f9 1d 02 00 00 7c e4 } 	condition:
		((#a_03_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 ]]

da79faee-066c-4f33-b3ab-11ef0f4e65ab

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