File and Directory Permissions Modification: Linux and Mac Permissions
- ID
- T1222.002
- Tactics
- TA0112 Defense Impairment
- Sub-technique of
- T1222 File and Directory Permissions Modification
- Platforms
- Linux, macOS
- Data sources
- File Metadata, Command Execution, Process Creation, File Modification
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.[1][2] File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).
Most Linux and Linux-based platforms provide a standard set of permission groups (user, group, and other) and a standard set of permissions (read, write, and execute) that are applied to each group. While nuances of each platform’s permissions implementation may vary, most of the platforms provide two primary commands used to manipulate file and directory ACLs: chown (short for change owner), and chmod (short for change mode).
Adversarial may use these commands to make themselves the owner of files and directories or change the mode if current permissions allow it. They could subsequently lock others out of the file. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via Unix Shell Configuration Modification or tainting/hijacking other instrumental binary/configuration files via Hijack Execution Flow.[3]
Detection
- DET0351 Unix-like File Permission Manipulation Behavioral Chain Detection Strategy
Data components: File Metadata, Command Execution, Process Creation, File Modification
Mitigations (2)
- M1022 Restrict File and Directory Permissions
Applying more restrictive permissions to files and directories could prevent adversaries from modifying the access control lists.
- M1026 Privileged Account Management
Ensure critical system files as well as those known to be abused by adversaries have restrictive permissions and are owned by an appropriately privileged account, especially if access is not required by users nor will inhibit system functionality.
Groups (4)
Software (11)
- S0281 Dok
- S0352 OSX_OCEANLOTUS.D
- S0402 OSX/Shlayer
- S0482 Bundlore
- S0587 Penquin
- S0598 P.A.S. Webshell
- S0599 Kinsing
- S0658 XCSSET
- S1070 Black Basta
- S1105 COATHANGER
- S9013 DRYHOOK
