MonitoringTool_Win32_Csysserv_3

YARA detection rule by roadwy

MonitoringTool:Win32/Csysserv,SIGNATURE_TYPE_PEHSTR,04 00 04 00 05 00 00

rule MonitoringTool_Win32_Csysserv_3{
	meta:
		description = "MonitoringTool:Win32/Csysserv,SIGNATURE_TYPE_PEHSTR,04 00 04 00 05 00 00 "
		
	strings :
		$a_01_0 = {49 45 47 75 61 72 64 2e 44 4c 4c 00 44 6c 6c 43 61 6e 55 6e 6c 6f 61 64 4e 6f 77 } 		$a_01_1 = {31 42 37 37 44 33 30 41 2d 38 31 43 39 2d 34 39 37 41 2d 38 36 34 37 2d 31 34 32 46 37 35 31 31 42 31 46 42 } 		$a_01_2 = {49 45 47 75 61 72 64 2e 49 45 57 65 62 47 75 61 72 64 2e 31 } 		$a_01_3 = {73 20 27 7b 35 41 42 30 44 32 36 36 2d 44 44 32 42 2d 34 30 30 36 2d 42 39 44 36 2d 41 39 31 34 35 32 39 31 42 44 44 36 } 		$a_01_4 = {49 45 57 65 62 47 43 55 53 54 4f 4d 5f } 	condition:
		((#a_01_0  & 1)*2+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1) >=4
 
}

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

8210cfe2-7228-4a0e-8761-a6cf9491af62

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