Linux setcap sets cap_setuid on a binary via setcap utility

Alerts on Linux executions of setcap configuring cap_setuid on a binary, indicating potential identity-manipulation and persistence risk.

FreeReviewedSigma · Low · v3
Product
linux
Category
process_creation
Author
Luc Génaux (SigmaHQ), DRL 1.1
Published
2026-01-24
Updated
2026-07-31

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule identifies process activity where the setcap utility is used to set the cap_setuid capability on a binary (via CommandLine containing cap_setuid and the executable path ending with /setcap). Granting cap_setuid allows a process to manipulate user IDs, potentially enabling execution paths that would otherwise be restricted. Telemetry required includes Linux process creation fields: the process image path and the command-line arguments.

Related detections9 linkedT1548 — drag to rearrange
Linux setcap sets cap_setgid on binaries (Setgid capability assignment)
Malicious Backdoored liblzma XZ Utils Library File via file_event
Suspicious User Home Directory Modification via dscl Process Creation
Possible GTFOBins Shell Breakout via apt Command
Malicious Update Orchestrator Service Reconfiguration for Privilege Escalation
Malicious macOS Credential Verification via dscl authonly
Malicious setcap Assigning cap_sys_admin for GameOverlay Privilege Escalation (via process_creation)
Suspicious Root Filesystem Remount as Writable on Appliance via Mount (via process_creation)
Suspicious AWS GetFederationToken Console Access by JavaGhost (via cloudtrail)
Linux setcap sets cap_setuid on a binary via setcap utility
Pivot detection · T1548 · 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.