malware_INetGet_exe

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

APT Malware using INetGet

rule malware_INetGet_exe
{
  meta:
    description = "APT Malware using INetGet"
    author = "JPCERT/CC Incident Response Group"
    hash = "d3f0af5ab7778846d0eafa4c466c11f11e4ee3b0dc359f732ba588c5a482dbf2"

	strings:
		$v1c = "cookie:flag=" wide
		$v1d = "LoRd_MuldeR" wide
		$w1a = "INetGet.exe" wide

	condition:
		all of them
}

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

e42b93ef-9726-492a-b0dd-30c7050532d6

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