DDoS_Win32_Nitol_Q_bit

YARA detection rule by roadwy

DDoS:Win32/Nitol.Q!bit,SIGNATURE_TYPE_PEHSTR_EXT,06 00 06 00 06 00 00

rule DDoS_Win32_Nitol_Q_bit{
	meta:
		description = "DDoS:Win32/Nitol.Q!bit,SIGNATURE_TYPE_PEHSTR_EXT,06 00 06 00 06 00 00 "
		
	strings :
		$a_01_0 = {83 c0 03 33 d2 0f af c6 f7 74 24 } 		$a_01_1 = {25 63 25 63 25 63 25 63 25 63 2e 65 78 65 00 } 		$a_01_2 = {48 41 52 44 57 41 52 45 5c 44 45 53 43 52 49 50 54 49 4f 4e 5c 53 79 73 74 65 6d 5c 43 65 6e 74 72 61 6c 50 72 6f 63 65 73 73 6f 72 5c 30 } 		$a_01_3 = {64 64 6f 73 2e 74 66 } 		$a_01_4 = {31 39 32 2e 31 36 38 2e 31 2e 32 34 34 } 		$a_01_5 = {52 65 66 65 72 65 72 3a 20 68 74 74 70 3a 2f 2f 25 73 25 73 } 	condition:
		((#a_01_0  & 1)*1+(#a_01_1  & 1)*1+(#a_01_2  & 1)*1+(#a_01_3  & 1)*1+(#a_01_4  & 1)*1+(#a_01_5  & 1)*1) >=6
 
}

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

5eb6718b-da6b-486c-b0e8-4601bb01f8c5

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