Suspicious su to Root with Blank Invoking User for CopyFail LPE (via auth)

PremiumReviewedSigma · Medium · v1
Product
linux
Service
auth
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects malformed su authentication records where the invoking username field is blank which the CopyFail exploit produces after patching /usr/bin/su in the page cache to grant a root shell without a valid caller. A su-to-root record missing its originating user is a strong tampering indicator of the runtime binary modification.

Related detections9 linkedT1068 — drag to rearrange
Suspicious su Execution From Uncommon Parent Process on Linux (via process_creation)
Linux sudo CVE-2019-14287 exploit attempt via unusual USER strings
Linux Sudo Privilege Escalation Attempt Matching CVE-2019-14287 Command-Line Pattern
Suspicious Delayed AF_ALG PF_ALG Protocol Registration for CopyFail LPE (via syslog)
Suspicious CrazyHunter BYOVD Driver Drop in Public Directory
Possible Container Escape via Working Directory Under proc CVE-2024-21626
Possible Sudo Heap Overflow Exploitation via sudoedit (CVE-2021-3156)
Suspicious dirty_sock Local Account Artifact From Snapd Privilege Escalation (via process_creation)
Suspicious Modification of Privileged Authentication Binaries via Kernel LPE
Suspicious su to Root with Blank Invoking User for CopyFail LPE (via auth)
Pivot detection · T1068 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.