Linux auditd: Hidden file or directory creation via leading-dot paths in execve

Alerts on Linux process executions creating or modifying dot-prefixed (hidden) files/directories.

FreeReviewedSigma · Low · v3
Product
linux
Service
auditd
Author
Pawel Mazur (SigmaHQ), DRL 1.1
Published
2021-09-06
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Linux processes that create or edit files by executing mkdir, nano, touch, vi, or vim with a path argument whose basename starts with a dot. Hidden (dot) files and directories are commonly used to reduce visibility and support stealthy persistence or configuration changes. It relies on auditd EXECVE telemetry capturing the command name and the first or second path-like argument matching a leading-dot pattern.

Related detections9 linkedT1564.001 — drag to rearrange
Suspicious File Hiding via attrib Hidden and System Attributes (via process_creation)
Suspicious File Hidden via attrib in Public Documents (via process_creation)
Suspicious Execution from Reserved Device Name Directory by Miner Campaign
Suspicious File Hiding via Attrib System and Hidden Attributes
Suspicious attrib Hidden and System Attribute Assignment
Suspicious File Hiding via attrib Plus H in Java RAT Persistence Setup
Suspicious Execution of Hidden Binary from Private Tmp via Process Creation
Suspicious Executable Written to User Documents Subfolder (via file_event)
Suspicious Sobolan Staging Directory Creation in var tmp (via file_event)
Linux auditd: Hidden file or directory creation via leading-dot paths in execve
Pivot detection · T1564.001 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.