T1036.011 Google Chronicle · YARA-L

Detect Overwrite Process Arguments in Google Chronicle

Adversaries may modify a process's in-memory arguments to change its name in order to appear as a legitimate or benign process. On Linux, the operating system stores command-line arguments in the process's stack and passes them to the main() function as the argv array. The first element, argv[0], typically contains the process name or path. By default, the Linux /proc filesystem uses this value to represent the process name. The /proc/<PID>/cmdline file reflects the contents of this memory, and tools like ps use it to display process information. During runtime, adversaries can erase the memory used by all command-line arguments for a process, overwriting each argument string with null bytes, then write a spoofed string into the memory region previously occupied by argv[0] to mimic a benign command. This technique is used by BPFDoor, which overwrites its argv[0] with names resembling Linux system daemons such as /sbin/udevd -d, dbus-daemon --system, and avahi-daemon: chroot helper.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1036 Masquerading
Sub-technique
T1036.011 Overwrite Process Arguments
Canonical reference
https://attack.mitre.org/techniques/T1036/011/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1036_011_overwrite_process_arguments {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects T1036.011 process argument overwriting where argv[0] (claimed process name) differs from the actual executable path and the claimed name impersonates a known Linux system daemon."
    mitre_attack_technique = "T1036.011"
    mitre_attack_tactic = "Defense Evasion"
    severity = "HIGH"
    confidence = "MEDIUM"
    reference = "https://attack.mitre.org/techniques/T1036/011/"

  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    $e.principal.process.command_line != ""
    $e.principal.process.file.full_path != ""
    $e.principal.process.command_line != $e.principal.process.file.full_path
    (
      re.regex($e.principal.process.command_line, `^(/sbin/udevd|dbus-daemon|avahi-daemon|auditd|systemd-journald|/sbin/rpcbind|xinetd|crond|atd|acpid|smartd|irqbalance)`)
      or not re.regex($e.principal.process.file.full_path, `^(/usr/|/bin/|/sbin/|/lib/)`)
    )

  condition:
    $e
}
high severity medium confidence

Chronicle YARA-L 2.0 rule detecting T1036.011 process argument overwriting on Linux. Compares the process command line (reflecting argv[0]) against the actual executable path in UDM PROCESS_LAUNCH events. Alerts when a process claims to be a known Linux system daemon but its real binary path does not match, or when the actual binary resides outside standard system directories.

Data Sources

Chronicle UDM — Linux auditd ingestion via Chronicle forwarderGoogle Chronicle Linux process telemetry

Required Tables

UDM PROCESS_LAUNCH events

False Positives & Tuning

  • Legitimate setproctitle() usage by applications such as PostgreSQL worker processes that rename themselves to reflect their current activity
  • Container runtimes or orchestration agents that spawn processes with display-friendly argv[0] values distinct from the actual binary
  • Custom hardening wrappers in non-standard paths that present a standard daemon name for compatibility with monitoring tools
Download portable Sigma rule (.yml)

Other platforms for T1036.011


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Overwrite argv[0] with Bash Process Substitution

    Expected signal: Auditd EXECVE record with a0='/sbin/udevd -d' but exe pointing to /usr/bin/sleep (or /bin/sleep). The ps output shows the spoofed name. /proc/<PID>/cmdline shows '/sbin/udevd -d' while /proc/<PID>/exe symlinks to the actual sleep binary.

  2. Test 2Python prctl PR_SET_NAME Process Rename

    Expected signal: Auditd SYSCALL record for prctl (syscall 157) with a0=15 (PR_SET_NAME) from python3. The /proc/<PID>/comm file will show 'avahi-daemon' while /proc/<PID>/exe still points to /usr/bin/python3. Process creation event shows python3 but ps output shows avahi-daemon.

  3. Test 3C Program argv[0] Overwrite and Fork (BPFDoor Simulation)

    Expected signal: Auditd EXECVE record for /tmp/df00tech_argv_test. Fork SYSCALL (57) record. PROCTITLE record changing to hex-encoded '/sbin/udevd -d'. The child process shows PPID=1 (adopted by init) with args='/sbin/udevd -d' but /proc/<PID>/exe -> /tmp/df00tech_argv_test.

Unlock Pro Content

Get the full detection package for T1036.011 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections