Cross-source coverage

T1547.011 / ATT&CK

Boot or Logon Autostart Execution: Plist Modification

ATT&CK has retired this technique. Rules still tag it; the current id is T1647 Plist File Modification.

3 rules across 2 sources.

From MITRE ATT&CK 19.2

Adversaries can modify property list files (plist files) to execute their code as part of establishing persistence. Plist files are used by macOS applications to store properties and configuration settings for applications and services. Applications use information plist files, Info.plist, to tell the operating system how to handle the application at runtime using structured metadata in the form of keys and values. Plist files are formatted in XML and based on Apple's Core Foundation DTD and can be saved in text or binary format.

Adversaries can modify paths to executed binaries, add command line arguments, and insert key/pair values to plist files in auto-run locations which execute upon user logon or system startup. Through modifying plist files in these locations, adversaries can also execute a malicious dynamic library (dylib) by adding a dictionary containing the DYLD_INSERT_LIBRARIES key combined with a path to a malicious dylib under the EnvironmentVariables key in a plist file. Upon user logon, the plist is called for execution and the malicious dylib is executed within the process space. Persistence can also be achieved by modifying the LSEnvironment key in the application's Info.plist file.

Platforms
macOS
Telemetry

elastic/detection-rules

2 rules
Detection Severity Format
Persistence via a Hidden Plist Filename High Elastic TOML
Persistence via Suspicious Launch Agent or Launch Daemon High Elastic TOML

panther-labs/panther-analysis

1 rule
Detection Severity Format
CrowdStrike MacOS plutil Novel Plist Modification (Anomaly Detection) Medium Panther Python

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.