_PseudoSigner_01_JDPack_1x__JDProtect_09__Anorganix_

YARA detection rule by HydraDragonAntivirus · GPL-2.0

PseudoSigner 0.1 [JDPack 1.x / JDProtect 0.9] --> Anorganix

import "pe"
rule _PseudoSigner_01_JDPack_1x__JDProtect_09__Anorganix_
{
	meta:
		description = "PseudoSigner 0.1 [JDPack 1.x / JDProtect 0.9] --> Anorganix"
	strings:
		$0 = {60 E8 22 00 00 00 5D 8B D5 81 ED 90 90 90 90 2B 95 90 90 90 90 81 EA 06 90 90 90 89 95 90 90 90 90 83 BD 45 00 01 00 01 E9}
	condition:
		$0 at pe.entry_point
}

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

ecf8f9b5-c392-41a0-890b-49f0eabc66e3

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