macOS Cron Task Abuse via crontab Executed from /tmp

Detects macOS cron scheduling activity where crontab is run with /tmp in the command line.

FreeReviewedSigma · Medium · v2
Product
macos
Category
process_creation
Author
Alejandro Ortuno, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-06
Updated
2026-07-31

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches process executions of crontab where the command line includes paths under /tmp, indicating cron job creation from a temporary directory. Attackers often use /tmp staging to drop or prepare scripts and then schedule them for initial or recurring execution. The detection relies on process creation telemetry that provides the executable path and full command line arguments.

Related detections9 linkedT1053.003 — drag to rearrange
Malicious Cron Execution of Binary from tmp Directory on Linux (via process_creation)
Suspicious Process Execution from Hidden Outlaw Config Directory
Suspicious Cron Reboot Persistence Pointing to Hidden User Directory on Linux
Suspicious Cron Job Downloading and Executing Payload via GlobalProtect Exploitation
Suspicious Remote Script Download Piped to Shell via 8220 Gang Hadooken
Suspicious Linux Crontab Reboot Persistence to Hidden Sys Cache Binary (via process_creation)
Suspicious Cron Persistence Installing a Downloader via Command Line
Suspicious Cron Persistence File Creation in System Cron Directories (via file_event)
Suspicious Cron Persistence via etc cron.d tsar (via file_event)
macOS Cron Task Abuse via crontab Executed from /tmp
Pivot detection · T1053.003 · 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.