Investigating Mac Persistence with BTM
Use the macOS BTM store in a malware or intrusion case: items with no developer, hidden items, unregistered plists, the notification, and a worked example.
Use the macOS BTM store in a malware or intrusion case: items with no developer, hidden items, unregistered plists, the notification, and a worked example.
Location, file versions and format of the macOS BTM store, how its records map to users, and the legacy backgrounditems.btm used from macOS 10.13 to 12.
How the BTM disposition differs from launchd's disabled.plist overrides on macOS, what each records, and how to read the combinations in an investigation.
How to collect the macOS Background Task Management store and sfltool dumpbtm output: Full Disk Access, root, and what Aftermath, UAC and Velociraptor take.
How to read sfltool dumpbtm: user sections, Type and Disposition bits, Flags, Developer Name, Team Identifier, Identifier, Generation and parent links.
How apps register login items, agents and daemons with SMAppService since macOS 13, how those differ from legacy plists, and how they appear in the BTM store.
What Background Task Management is, which login items, agents and daemons it tracks since macOS 13 Ventura, what a record holds and what it cannot prove.