Linux cron: Suspicious crontab modification with REPLACE

Alerts on Linux cron activity indicating crontab changes containing the keyword "REPLACE".

FreeReviewedSigma · Medium · v3
Product
linux
Service
cron
Author
Pawel Mazur (SigmaHQ), DRL 1.1
Published
2022-04-16
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 Linux cron-related activity containing the keyword "REPLACE", which is indicative of a crontab being modified in a way that may be suspicious. Attackers can use cron persistence by altering scheduled tasks to execute commands at defined intervals. The detection relies on cron service telemetry that includes the matching keyword in the event data.

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: Suspicious crontab modification with REPLACE
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.