Linux sudo --chroot Command Execution

Identifies Linux executions of sudo with chroot-related options ("--chroot" or "-R") via process creation command-line telemetry.

FreeReviewedSigma · Low · v3
Product
linux
Category
process_creation
Author
Swachchhanda Shrawn Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-10-02
Updated
2026-07-31

ATT&CK techniques

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 process executions where the command line includes sudo’s --chroot-related options (e.g., “ --chroot ” or “sudo -R ”) when the process image ends with /sudo. Attackers can use chroot to run commands in an alternate filesystem view while operating under elevated privileges, which can complicate monitoring and incident response. It relies on process creation telemetry with the executable path and command-line arguments.

Related detections9 linkedT1068 — drag to rearrange
Malicious JuicyPotato Privilege Escalation Execution (UAT-7237)
Suspicious Dell ControlVault DLL Load by Unexpected Process (ReVault)
Malicious Known Vulnerable Driver Load for BYOVD Attack
Suspicious Vulnerable ASUS AsIO3.sys Driver Load
Malicious Qilin EDR Killer BYOVD Driver Load
Malicious Looney Tunables Privilege Escalation Exploit by Kinsing (via process_creation)
Malicious Kerberos proxiable/S4U2self Ticket - CVE-2021-42278/42287 (via security)
Malicious Vulnerable Driver HwRwDrv Loaded for BYOVD
Possible CopyFail Root Exploitation via Python Spawning SUID Shell (via process_creation)
Linux sudo --chroot Command Execution
Pivot detection · T1068 · 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.