Linux Masquerading via crond Path Using cp Launching /bin/sh

Alerts on Linux execve where cp runs through /bin/sh and the argument ends with /crond, indicating potential masquerading.

FreeReviewedSigma · Medium · v3
Product
linux
Service
auditd
Author
Timur Zinniatullin, oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-21
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. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches process executions where cp is invoked to run /bin/sh and the command argument ends with /crond. Such behavior can indicate masquerading, where attackers abuse executable naming or placement to evade monitoring and make activity resemble a legitimate cron-related process. It relies on Linux auditd telemetry capturing execve fields (process type and argv content).

Related detections9 linkedT1036.003 — drag to rearrange
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Linux Masquerading via crond Path Using cp Launching /bin/sh
Pivot detection · T1036.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.