MITRE ATT&CK / Techniques / T1647

Plist File Modification

ID
T1647
Tactics
TA0112 Defense Impairment
Platforms
macOS
Data sources
File Modification, Process Creation, Command Execution
Source
attack.mitre.org
MITRE last modified
12 May 2026

Adversaries may modify property list files (plist files) to enable other malicious activity, while also potentially evading and bypassing system defenses. macOS applications use plist files, such as the info.plist file, to store properties and configuration settings that inform the operating system how to handle the application at runtime. Plist files are structured metadata in key-value pairs formatted in XML based on Apple's Core Foundation DTD. Plist files can be saved in text or binary format.[2]

Adversaries can modify key-value pairs in plist files to influence system behaviors, such as hiding the execution of an application (i.e. Hidden Window) or running additional commands for persistence (ex: Launch Agent/Launch Daemon or Re-opened Applications).

For example, adversaries can add a malicious application path to the ~/Library/Preferences/com.apple.dock.plist file, which controls apps that appear in the Dock. Adversaries can also modify the LSUIElement key in an application’s info.plist file to run the app in the background. Adversaries can also insert key-value pairs to insert environment variables, such as LSEnvironment, to enable persistence via Dynamic Linker Hijacking.[3][4]

Detection

Mitigations (1)

M1013 Application Developer Guidance

Ensure applications are using Apple's developer guidance which enables hardened runtime.[1]

Software (2)

References

  1. Apple Developer Doco Hardened Runtime
  2. fileinfo plist file description
  3. wardle chp2 persistence
  4. eset_osx_flashback