SUSP_Export_Offset_Undefined

YARA detection rule by Greg Lesnewich · GPL-2.0

check for files that have at least 1 export that has an no defined offset or other fields

import "pe"
rule SUSP_Export_Offset_Undefined {
  meta:
    author      = "Greg Lesnewich"
    description = "check for files that have at least 1 export that has an no defined offset or other fields"
    date        = "2023-01-14"
    version     = "1.0"
    DaysofYARA  = "14/100"

  condition:
    for any exp in pe.export_details: (
      not defined exp.offset and
      not defined exp.name and
      not defined exp.forward_name
    )
}

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

2fd8be6b-2c87-4f09-b112-e3f70a4f37e4

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