tick_app_js

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

JavaScript malware downloaded using a vulnerability in SKYSEA

rule tick_app_js {
      meta:
        description = "JavaScript malware downloaded using a vulnerability in SKYSEA"
        author = "JPCERT/CC Incident Response Group"
        hash = "f36db81d384e3c821b496c8faf35a61446635f38a57d04bde0b3dfd19b674587"

  	  strings:
      	$sa = "File download error!"
        $sb = "/tools/uninstaller.sh"
        $sc = "./npm stop"

      condition:
      	all of them
}

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

1a76399e-5f58-4175-bcec-bfb1ef02132a

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