Techniques › T1480.002 › AN0373
AN0373 Analytic 0373
Linux · attack.mitre.org · ATT&CK Enterprise v19.2
<p>File lock acquired via open() + flock() or lockf() on predictable path (e.g., /tmp/.lock123) followed by conditional early exit or divergent process behavior.</p>
- Detects
- T1480.002 Mutual Exclusion
- Part of
- DET0132 Detection of Mutex-Based Execution Guardrails Across Platforms
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| auditd:SYSCALL | open, flock, fcntl, unlink | DC0055 File Access |
| auditd:SYSCALL | exit_group | DC0033 Process Termination |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
lockfile_path_regex | Detect patterns like /tmp/.lock*, /var/run/*lock used by malware. |
exit_code | Track specific exit codes (e.g., 1, 2) that signal lock acquisition failure. |
TimeWindow | Correlate lockfile access + early process termination within N seconds. |