Masquerading Execution of Binary from Var Log Directory (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-07-09
Updated
2026-08-28

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects execution of an executable located under the var log directory on Linux, the persistence staging behavior of the Kimsuky Gomir variant which copies its binary to var log rsyslogd and runs it through a systemd service. Adversaries leverage a log directory that normally holds only text logs to hide an executable while masquerading as the rsyslog daemon, making early detection critical for surfacing the implant before it beacons.

Related detections9 linkedT1543.002 — drag to rearrange
Malicious Systemd Service Masquerading as Sd-Pam Helper
Malicious Linux systemd Persistence nvmconf.service
Suspicious Linux Persistence via sed Edit of Boot and Init Files
Suspicious systemd Service Persistence via GRIDTIDE xapt
Suspicious Python Execution of Fake Sysmon Script From Config Directory
Suspicious Linux Boot Persistence via rc.local or init.d Modification (via file_event)
Malicious systemd-daemon Masquerading Binary Execution on Linux
Suspicious Masquerading systemd Unit display-managerd Creation via File System
Suspicious Systemd Service Unit Written to System Directory (via process_creation)
Masquerading Execution of Binary from Var Log Directory (via process_creation)
Pivot detection · T1543.002 · 9 related

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