Cross-source coverage
T1546.017 / ATT&CK
Event Triggered Execution: Udev Rules
3 rules across 1 source.
From MITRE ATT&CK 19.2
Adversaries may maintain persistence through executing malicious content triggered using udev rules. Udev is the Linux kernel device manager that dynamically manages device nodes, handles access to pseudo-device files in the /dev directory, and responds to hardware events, such as when external devices like hard drives or keyboards are plugged in or removed. Udev uses rule files with match keys to specify the conditions a hardware event must meet and action keys to define the actions that should follow. Root permissions are required to create, modify, or delete rule files located in /etc/udev/rules.d/, /run/udev/rules.d/, /usr/lib/udev/rules.d/, /usr/local/lib/udev/rules.d/, and /lib/udev/rules.d/. Rule priority is determined by both directory and by the digit prefix in the rule filename.
Adversaries may abuse the udev subsystem by adding or modifying rules in udev rule files to execute malicious content. For example, an adversary may configure a rule to execute their binary each time the pseudo-device file, such as /dev/random, is accessed by an application. Although udev is limited to running short tasks and is restricted by systemd-udevd's sandbox (blocking network and filesystem access), attackers may use scripting commands under the action key RUN+= to detach and run the malicious content’s process in the background to bypass these controls.
- Tactics
- Persistence · Privilege Escalation
- Platforms
- Linux
- Telemetry
-
auditd:SYSCALLauditd:CONFIG_CHANGE
How MITRE says to detect it DET0375
Detection Strategy for T1546.017 - Udev Rules (Linux)
Linux Analytic 1056
Monitor for creation or modification of udev rules files in key directories (/etc/udev/rules.d/, /lib/udev/rules.d/, /usr/lib/udev/rules.d/). Look for RUN+= or IMPORT keys invoking suspicious binaries or scripts. Correlate this with process execution from systemd-udevd context, and file writes near udev reload/restart events. Combine this with unexpected background process spawning from udevd-related forks.
auditd:SYSCALLchmod, write, create, openauditd:SYSCALLexecveauditd:CONFIG_CHANGEudev rule reload or trigger command executed
elastic/detection-rules
3 rules| Detection | Severity | Format |
|---|---|---|
| Executable Bit Set for Potential Persistence Script | Medium | Elastic TOML |
| Potential Persistence via File Modification | Low | Elastic TOML |
| Systemd-udevd Rule File Creation | Low | Elastic TOML |