Linux Cron Directory File Creation via File Events

Flags new Linux cron-related files created under standard cron directories, excluding a few known benign paths.

FreeReviewedSigma · Low · v3
Product
linux
Category
file_event
Author
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research), MSTIC (SigmaHQ), DRL 1.1
Published
2021-10-15
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 identifies file creations targeting common Linux cron locations and cron-related control files, which can be used to establish scheduled execution as persistence. Such changes are important because attackers may add new cron entries or modify scheduling by writing files in cron directories. It relies on Linux file event telemetry containing TargetFilename values that match cron directories and special cron files, with optional exclusions for known benign entries.

Related detections9 linkedT1053.003 — drag to rearrange
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)
Suspicious Cron Job Executing Binary From var tmp via Process Creation
Suspicious Cron Job Persistence Creation on Linux (via process_creation)
Suspicious Cron Persistence File Created in System Cron Directories
Linux Cron Directory File Creation via File Events
Pivot detection · T1053.003 · 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.