VirTool_Win32_CeeInject_OJ_bit

YARA detection rule by roadwy

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

rule VirTool_Win32_CeeInject_OJ_bit{
	meta:
		description = "VirTool:Win32/CeeInject.OJ!bit,SIGNATURE_TYPE_PEHSTR_EXT,02 00 02 00 02 00 00 "
		
	strings :
		$a_03_0 = {79 05 4a 83 ca ?? 42 85 d2 75 ?? 8b 45 ?? 83 c0 ?? 89 45 ?? 8b 4d ?? 03 4d ?? 8b 55 ?? 8a 82 ?? ?? ?? ?? 88 01 } 		$a_03_1 = {8b ec 51 8b 45 0c 89 45 fc 8b 4d 08 33 4d fc 89 4d 08 8b 55 fc 83 c2 ?? 89 55 fc 8b 45 08 2d ?? ?? ?? ?? 89 45 08 8b 4d fc 81 e9 ?? ?? ?? ?? 89 4d fc c1 4d 08 ?? 8b 45 08 } 	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 ]]

98ee6b92-3042-4802-85ae-996a989c005c

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