Linux: Shell Command Execution Using flock -u with Common Shell Paths

Flags Linux process creation where flock is invoked with a user option and common shell paths on the command line.

FreeReviewedSigma · High · v3
Product
linux
Category
process_creation
Author
Li Ling, Andy Parkidomo, Robert Rakowski, Blake Hartstein (Bloomberg L.P.) (SigmaHQ), DRL 1.1
Published
2024-09-02
Updated
2026-07-31

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies executions of the Linux flock utility where the command line includes ' -u ' and references common interactive shell binaries (/bin/bash, /bin/dash, /bin/fish, /bin/sh, /bin/zsh). This matters because flock can be used to run shell commands in contexts where attackers seek unauthorized execution or environment escape. The detection relies on process creation telemetry with access to the executable path (ending in /flock) and the full command line string.

Related detections9 linkedT1083 — drag to rearrange
Possible Nagios XI Path Traversal via Graphtemplates Directory Parameter
Suspicious Credential String Enumeration via findstr to Temp Directory
Suspicious ipconfig Reconnaissance Output Redirected to CentreStack Log File
Possible osTicket PHP Filter Chain Injection via Anonymous Ticket Endpoints (via webserver)
Possible Local File Inclusion Path Traversal Targeting CentreStack Web.config
PUA: TruffleHog Execution on Windows via trufflehog.exe Process Launch
Linux Process Execution of TruffleHog with Secret-Scanning Platforms
Windows: Notepad Password File Discovery via Process Creation
Linux process execution of shell via nice utility
Linux: Shell Command Execution Using flock -u with Common Shell Paths
Pivot detection · T1083 · 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.