Win_Trojan_Eybog_1

YARA detection rule by HydraDragonAntivirus · GPL-2.0

Rule Win_Trojan_Eybog_1 (No description metadata provided).

rule Win_Trojan_Eybog_1
{
strings:
	$a0 = { 536c656570 }

	$a1 = { 4765744c6f63616c54696d65 }

	$a2 = { 47657453746172747570496e666f41 }

	$a3 = { 487474704f70656e5265717565737441 }

	$a4 = { 3132372e302e302e31[0-23]4d6f7a696c6c612f342e30 }


condition:
	$a0 and $a1 and $a2 and $a3 and $a4
}

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

f79e2df8-560c-4f25-bcd8-2d61f16b55b4

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