Skip to content

Reading sfltool dumpbtm Output Field by Field

How to read sfltool dumpbtm: user sections, Type and Disposition bits, Flags, Developer Name, Team Identifier, Identifier, Generation and parent links.

Published on 8 min read
On this page

TL;DR. sudo sfltool dumpbtm prints the Background Task Management store: one section per user (Records for UID <n> : <generated UID>), then one numbered record per item. The fields that matter most are Type (a bit field: 0x2 app, 0x4 login item, 0x8 agent, 0x10 daemon, 0x20 developer, plus a 0x10000 legacy modifier), Disposition (0x1 enabled, 0x2 allowed, 0x4 hidden, 0x8 notified), Developer Name and Team Identifier (attribution from the code signature), URL and Executable Path (what it runs), and Parent Identifier (which app or developer it belongs to). None of the bits are documented by Apple; they are read from the names sfltool prints next to each hex value. BTM Parser parses this text into the same table as the store file.

Running it

sudo sfltool dumpbtm > btm.txt

Apple's deployment guide names sfltool dumpbtm as the way to print the current status of login and background items, including the UUIDs of loaded service management payloads. sfltool lives in /usr/bin, and its man page describes it as a tool for testing and debugging SharedFileList. The page predates BTM and does not mention dumpbtm; the tool's usage line on recent releases simply lists dumpbtm and resetbtm among its subcommands. Run without sudo, it is reported to ask for administrator authorization. The format is not a stable interface. Spacing, the order of lines and some wording change between releases, so read every field by its label, not by its position.

Never confuse it with sfltool resetbtm, which resets the store.

The structure

========================
 Records for UID 501 : 6E1C7B52-3F0A-4D21-9B8E-2C5A7D9E4F13
========================

 Items:

 #11:
                 UUID: 0B7E2C4A-91D3-4F6B-8A2E-5C3D0000000B
                 Name: com.example.updater
       Developer Name: (null)
                 Type: legacy agent (0x10008)
          Disposition: [enabled, allowed, visible, notified] (0xb)
           Identifier: 8.com.example.updater
                  URL: file:///Users/dana.whitlock/Library/LaunchAgents/com.example.updater.plist
      Executable Path: /Users/dana.whitlock/Library/Application Support/.updater/sync-helper
           Generation: 1
    Parent Identifier: Unknown Developer

This is the planted agent as it appears in the dumpbtm text of the FIN-MBP-03 sample (the second sample in BTM Parser). Real output from recent releases has the same shape; it also prints Team Identifier and Flags lines where the record has them, and a few header lines before the items (ServiceManagement migrated, and on recent builds LaunchServices registered). Each user section starts with the numeric UID and the user's generated UID, the key the store files records under. The # numbers are positions in the list, not identifiers.

Field by field

UUID and Name

UUID identifies the record. Use it to refer to the item in notes. Name is a display name: the app name for app records, often the launchd label or the executable name for legacy items. A name is easy to fake; a team identifier in a valid Developer ID signature is not, since it comes from a certificate Apple issued to that team.

Developer Name and Team Identifier

These come mostly from the code signature. For well-known helpers, the developer name can also come from an attribution list Apple ships with the framework (attributions.plist), which maps their labels to a product name and team identifier. Apple's documentation says that for a legacy plist without AssociatedBundleIdentifiers, System Settings shows the organization name from the app's signing certificate; when the executable is not signed and cannot be attributed, it shows the executable name. The team identifier is the 10-character ID Apple assigns to a developer team, which codesign -dv prints as TeamIdentifier. Apple's own platform binaries have none: codesign prints TeamIdentifier=not set for them.

Read the two fields together. DumpBTM's published example shows an app record with Developer Name: (null) and a valid team identifier, so an empty name alone means little. (null) in both means BTM attributed the item to no developer. That happens for unsigned and ad-hoc signed code, which includes plenty of legitimate open-source tools, and for most malware dropped as a bare executable. A team identifier that does not match the vendor the name suggests is the stronger signal.

Type

BitPrinted asStatus
0x1user itemName used in Apple's Endpoint Security types; bit value inferred, not documented
0x2appSeen in published output, e.g. app (0x2)
0x4login itemReported
0x8agentReported, e.g. legacy agent (0x10008)
0x10daemonSeen in published output, e.g. curated legacy daemon (0x90010)
0x20developerReported; a grouping record, not a program
0x10000legacy (prefix)A plist installed directly in a launchd folder
0x80000curated (prefix)Seen in published output; in that example the item is one listed in Apple's own attribution file

Endpoint Security, which Apple does document, describes BTM items with a type (user item, app, login item, agent, daemon) and two booleans, legacy and managed. Recent builds of the daemon also contain type names such as dock tile, quicklook and spotlight, and a managed prefix, whose bit values are not published. BTM Parser keeps the raw value next to the decoded name, and shows bits it cannot name as hex rather than guessing.

Flags

A second bit field, printed as a list of names and a value. [ ] (0) is common. Apple does not document its bits. Record what is printed and do not build conclusions on it.

Disposition

BitSetClear
0x1enableddisabled
0x2alloweddisallowed
0x4hiddenvisible
0x8notifiednot notified

The mapping is observable in any dump, because the names are printed next to the value: Howard Oakley published [enabled, allowed, not notified] (0x3), and DumpBTM's example shows [enabled allowed visible notified] (11). Published output comes in more than one style: some lists visible for an item that is not hidden, some leaves it out, and the value is printed in hex or in decimal. BTM Parser reads all of these; its sample text lists visible and prints hex. Common values:

ValueReads as
0x3enabled, allowed, not notified
0xbenabled, allowed, notified
0xaallowed, notified, but disabled
0xfenabled, allowed, hidden, notified

What turns each bit on or off is not documented. Every item has a switch in Login Items, but Apple does not say which bit the switch changes. In the FIN-MBP-03 sample, the Zoom updater that dana.whitlock switched off reads 0xa: allowed and notified, not enabled. Test the behaviour on a lab Mac of the same release before you put it in a report.

Identifier

BTM's key for the item. Its form varies. Often it is the type number, a dot and a bundle ID or label: 2.com.runningwithcrayons.Alfred for an app in Howard Oakley's published output, 8.com.example.updater for the agent above. Some records use a plain name instead, and DumpBTM's example shows a code requirement string for an app. Use it to follow links between records.

URL and Executable Path

URL points at what the item stands for: the plist of a legacy agent or daemon, the bundle of an app. Apple's Endpoint Security documentation notes that an item URL can be relative to the app it belongs to, which is how items inside app bundles appear. Executable Path is the program a launchd item runs, taken from the plist's Program or ProgramArguments. Check that the plist still exists, what it says now, and where the executable lives.

Generation

A counter. Apple does not document it. It is not a count of launches and not a time.

Bundle Identifier and Assoc. Bundle IDs

Bundle Identifier is printed for app records. Assoc. Bundle IDs lists the bundle identifiers the item is associated with. The documented source of that association is the AssociatedBundleIdentifiers key of a legacy plist, which tells the Login Items pane which app a helper belongs to. Apple requires the team identifier of the helper's executable to match the app's for that association to apply.

Parent Identifier and Embedded Item Identifiers

These link records into a tree. An app record lists the identifiers of its helpers under Embedded Item Identifiers, and each helper names the app in Parent Identifier. Developer records appear to play the same role for legacy items grouped by developer: DumpBTM's example shows Parent Identifier: Adobe Creative Cloud on a daemon. An item that could not be attributed shows Parent Identifier: Unknown Developer, as the FIN-MBP-03 agent does.

Text or file?

The text is what sfltool chooses to print, and only a live Mac can produce it. The store file can hold properties the text does not show. When you can, keep both. The commands are in collecting the BTM store.

BTM Parser accepts either. It reads the dump into the same item model as the file, tolerates spacing and wording differences, and tells you when it meets a line it does not understand instead of dropping it silently.

FAQ

What does Disposition 0xb mean in sfltool dumpbtm?

0xb is 0x1 + 0x2 + 0x8: enabled, allowed and notified, and not hidden. It is the usual state of a third-party item after the user was notified about it.

What does legacy agent (0x10008) mean?

0x8 is the agent bit and 0x10000 the legacy bit: a launch agent whose plist was installed directly in a LaunchAgents folder, not registered by an app through SMAppService.

Is sfltool dumpbtm documented by Apple?

Apple's deployment guide names it as the command that prints the current status of login and background items, including loaded service management payload UUIDs. The output format is not documented, and the sfltool man page predates it.

Why do I see Developer Name (null)?

Look at Team Identifier too. If both are (null), BTM could not attribute the item to a developer, usually because the executable is unsigned, ad-hoc signed, or not signed with a Developer ID, and the item is often under the parent identifier Unknown Developer. An app record can show a (null) developer name with a valid team identifier.

Frequently asked questions

What does Disposition 0xb mean in sfltool dumpbtm?

0xb is 0x1 + 0x2 + 0x8: enabled, allowed and notified, and not hidden. It is the usual state of a third-party item after the user was notified about it.

What does legacy agent (0x10008) mean?

0x8 is the agent bit and 0x10000 the legacy bit: a launch agent whose plist was installed directly in a LaunchAgents folder, not registered by an app through SMAppService.

Is sfltool dumpbtm documented by Apple?

Apple's deployment guide names it as the command that prints the current status of login and background items, including loaded service management payload UUIDs. The output format is not documented, and the sfltool man page predates it.

Why do I see Developer Name (null)?

Look at Team Identifier too. If both are (null), BTM could not attribute the item to a developer, usually because the executable is unsigned, ad-hoc signed, or not signed with a Developer ID, and the item is often under the parent identifier Unknown Developer. An app record can show a (null) developer name with a valid team identifier.