Skip to content

Offline · nothing is uploaded

Read what macOS registered to run.

Since macOS 13, Background Task Management records every login item, launch agent and daemon a Mac registers. See each one with its user, developer, team ID and disposition, joined to its launch plist, and what deserves a look first.

Drop a BTM store, a dumpbtm text or a collection

BackgroundItems-v*.btm, sudo sfltool dumpbtm output, a legacy backgrounditems.btm, or a .zip, .tar.gz or folder holding /private/var/db and the launch plists. User records and launch plists in a collection name the users and complete each item.

Collect the BTM data

The store sits in /private/var/db/com.apple.backgroundtaskmanagement, which macOS protects even from root: give Terminal Full Disk Access first (System Settings › Privacy & Security › Full Disk Access), then run one of these as an administrator.

  1. Copy the store or run the collection
  2. Drop the files here
  3. Read in your browser, never uploaded
Terminal · zsh / bash · admin
cd ~/Desktop && sudo sh -c 'tar -czf "btm-$(hostname -s).tar.gz" /private/var/db/com.apple.backgroundtaskmanagement /private/var/db/dslocal/nodes/Default/users /Library/LaunchAgents /Library/LaunchDaemons /Users/*/Library/LaunchAgents /Users/*/Library/Application\ Support/com.apple.backgroundtaskmanagementagent /Library/Preferences/SystemConfiguration/preferences.plist /System/Library/CoreServices/SystemVersion.plist 2>/dev/null; sfltool dumpbtm > "btm-$(hostname -s).txt"; ls -l btm-*'

Archives the BTM folder, the local user records, the launch plists and the host files, and saves sfltool's dump next to it. Drop both files here; the dump is matched to the store record by record.

Before you start

  • Never run sfltool resetbtm on a Mac under investigation: it resets the store, and the records are gone.
  • Without Full Disk Access, cp and tar report “Operation not permitted” for the BTM folder.
  • The collection holds the local user records, which include password hashes: treat it as evidence. The tool reads only names, UIDs, home folders, shells, real names and generateduids.

What is Background Task Management?

Since macOS 13 Ventura, the backgroundtaskmanagementd daemon keeps a record of the login items, launch agents and launch daemons it sees, with the developer name and team ID taken from the code signature and a disposition: enabled or not, allowed or not, visible or hidden, notified or not. System Settings › General › Login Items is built from it, and so are the “Background Items Added” notifications.

The records sit in /private/var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v<N>.btm, a binary property list written with NSKeyedArchiver, one section per user; sudo sfltool dumpbtm prints them as text. For an investigation it answers what was set to run on the Mac, for which user, signed by which developer, and whether it is still switched on.

How the tool reads it

  • The store is decoded in your browser: the keyed archive is unpacked, records are recognised by their shape and read through the field names each version has used, so stores from different macOS versions read the same way. Every field is also kept as recorded.
  • sfltool dumpbtm text is parsed into the same items; lines it does not understand are listed with their line numbers instead of being dropped silently.
  • Each user section is named from the local user records (generateduid and UID) when they are in the collection.
  • Items are joined to the launch plists of the collection by the path BTM recorded; plists no record points to are listed as not registered.
  • When a Mac has several BTM files (the store and its dump, or an older store version), the newest store is the reference and the same record elsewhere is noted on it, not listed twice.

What it reads

  • BackgroundItems-v*.btm stores, whatever the version number in the name
  • The output of sudo sfltool dumpbtm
  • The legacy per-user store of macOS 10.13 to 12 (backgrounditems.btm): item names and target paths, rebuilt from their bookmarks
  • Local user records (/private/var/db/dslocal/nodes/Default/users): name, UID, home, shell, real name and generateduid, never the password hash
  • Launch agents and daemons in /Library and in the home folders
  • Host name and macOS version, from SystemConfiguration/preferences.plist and SystemVersion.plist
  • Folders, .zip and .tar.gz collections, and files handed over by Disk Image Parser

Limits

  • Apple does not document the store. Type and disposition bits are named as sfltool prints them; bits without a known name are shown in hex, and unknown fields are shown raw.
  • A record that carries a date is shown with it, but the stores this tool was built and tested on carry none per item, so it does not date registrations: it shows when the store and the plists were last modified instead.
  • Code signatures are not verified: developer names and team IDs are what BTM recorded.
  • Apps that register helpers with SMAppService keep the plist inside their bundle; the tool shows the record, not that plist.
  • MDM payloads and per-user settings are shown as recorded, not interpreted.
  • A flag is a reason to look, not a verdict.

Questions

Are my files uploaded?

No. The page reads the files in your browser with JavaScript in a Web Worker; nothing is sent to a server. You can disconnect from the network once the page has loaded.

Why does copying the store need Full Disk Access?

macOS protects /private/var/db/com.apple.backgroundtaskmanagement with its privacy controls, even from root. Terminal needs Full Disk Access for cp, tar or sfltool to read it.

The store or sfltool dumpbtm: which should I use?

Both when you can. The store is the evidence itself and keeps every field; the dump is what sfltool chooses to print, but it is all you need when you can run a command and cannot copy files. Dropped together, they are matched record by record.

Which macOS versions are covered?

The BTM store of macOS 13 Ventura and later (the number in BackgroundItems-v<N>.btm changes between releases; records are recognised by shape, not by version) and the legacy per-user login items store of macOS 10.13 to 12.

Can it read a disk image?

Export /private/var/db, /Library and the home folders with Disk Image Parser or another forensic tool and drop the folder here. The page also accepts files handed over by Disk Image Parser, tab to tab, without a server.

What does “Unknown Developer” mean?

BTM had no developer to attach to the item, usually because its program is not signed with a Developer ID. The tool flags items that have neither a developer name nor a team ID.