Backdoor_Win32_Pirpi_A

YARA detection rule by roadwy

Backdoor:Win32/Pirpi.A,SIGNATURE_TYPE_PEHSTR_EXT,01 00 01 00 02 00 00

rule Backdoor_Win32_Pirpi_A{
	meta:
		description = "Backdoor:Win32/Pirpi.A,SIGNATURE_TYPE_PEHSTR_EXT,01 00 01 00 02 00 00 "
		
	strings :
		$a_03_0 = {8b cb 7d 12 8a 5c 0c ?? 32 da 80 c2 02 88 5c 0c ?? 41 3b c8 7c ee } 		$a_01_1 = {75 60 8d 56 07 33 c9 8a 02 3c 30 7c 0f 3c 39 7f 0b } 	condition:
		((#a_03_0  & 1)*1+(#a_01_1  & 1)*1) >=1
 
}

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

de6ba4d5-6c2d-40f1-8655-fb56eae4fe4d

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