malware_SysrvBot

YARA detection rule by JPCERT/CC Incident Response Group · NOASSERTION

detect SysrvBot

rule malware_SysrvBot {
    meta:
        description = "detect SysrvBot"
        author = "JPCERT/CC Incident Response Group"
        hash1 = "9df43de4920699bd51d4964b681bd2ce8315b189b812f92084f7c3e423610b2f"
        hash2 = "506d0ed05c5334cf4461380123eab85e46398220ed82386745f3d8ef3339adf9"

    strings:
        $a1 = "hello/controller/xmrig"
        $a2 = "hello/scan.(*Scanner)."
        $a3 = "hello/exp/exploit.go"

    condition:
        all of them
}

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

17453d13-5da8-4d9e-9b73-0f58a0ebbda1

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