Suspicious Linux Process Execution From /tmp Directory

Flags execution of binaries located under /tmp on Linux, excluding a known Nextcloud path.

FreeReviewedSigma · Medium · v2
Product
linux
Category
process_creation
Author
Joseliyo Sanchez, @Joseliyo_Jstnk (SigmaHQ), DRL 1.1
Published
2023-06-02
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. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Linux process creations where the process image path starts with /tmp/, indicating the executable was launched from a temporary directory. Attackers often use /tmp to run dropped payloads or execute tools that avoid well-known install locations. The detection relies on Linux process creation telemetry that includes the executed image path.

Related detections9 linkedT1036 — drag to rearrange
Suspicious Rclone Exfiltration Masquerading as wininit.exe
Suspicious Executable Running from Public Pictures Directory
Suspicious Python Execution via Renamed Synaptics Binary
Agent Tesla Persistence via Realtek Named Scheduled Task Batch
Suspicious Interlock Fake Updater Executable Execution
Malicious User Account Created by a Computer Account (via security)
Suspicious Execution of agent.exe From WinSyncDefender AppData Directory (via process_creation)
Malicious Scheduled Task Masquerading as Auto Update via schtasks (via process_creation)
Suspicious Novaservice Binary Executing From Public User Directory (via process_creation)
Suspicious Linux Process Execution From /tmp Directory
Pivot detection · T1036 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.