Need help with SwiftBelt?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

160 Stars 20 Forks BSD 3-Clause "New" or "Revised" License 76 Commits 2 Opened issues


A macOS enumeration tool inspired by harmjoy's Windows-based Seatbelt enumeration tool. Author: Cedric Owens

Services available


Need anything else?

Contributors list



SwiftBelt is a macOS enumerator inspired by @harmjoy's Windows-based Seatbelt enumeration tool. SwiftBelt does not utilize any command line utilities and instead uses Swift code (leveraging the Cocoa Framework, Foundation libraries, OSAKit libraries, etc.) to perform system enumeration. This can be leveraged on the offensive side to perform enumeration once you gain access to a macOS host. I intentionally did not include any functions that cause pop-ups (ex: keychain enumeration).

Thanks Ramos04 for contributing code to look for various Objective See tools and mattreduce for contributing code for zshell history as well as azure creds.



  1. Ensure swift is installed on your macOS host

  2. From a terminal cd into the SwiftBelt directory and run: "swift build" to generate the binary. The binary will be dropped in the .build/debug folder inside of the SwiftBelt folder and will be named SwiftBelt

  3. Copy to the desired host and clear the quarantine attribute ($ xattr -c SwiftBelt) and set as executable ($ chmod +x SwiftBelt)

  4. Execute

Help menu:

SwiftBelt Options:

-CheckFDA --> Check for Full Disk Access (without generating a TCC prompt to the user even if Terminal has not been granted any TCC permissions). Does this by doing a simple check on the user's TCC.db. Will return wither FDA has already been granted to Terminal or not.

-SecurityTools --> Check for the presence of common macOS security tools (at least the ones I am familiar with)

-SystemInfo --> Pull back system info (wifi SSID info, open directory node info, internal IPs, ssh/aws/gcloud/azure-cli cred info, basic system info). If present on the host, this tool will display the contents of ssh keys, known hosts file, aws cred files, and gcloud token info

-Clipboard --> Dump clipboard contents

-RunningApps --> List all running apps

-ListUsers --> List local user accounts

-LaunchAgents --> List launch agents, launch daemons, and configuration profile files

-BrowserHistory --> Attempt to pull Safari, Firefox, Chrome, and Quarantine history (note as FYI: if Chrome or Firefox is actively running, the tool will not be able to read the locked database to extract info). However, the locked db can be copied elsewhere and read from.

-SlackExtract --> Check if Slack is present and if so read cookie, downloads, and workspaces info (leverages research done by Cody Thomas)

-ShellHistory --> Read shell (Bash or Zsh) history content

-Bookmarks --> Read Chrome saved bookmarks

-ChromeUsernames --> Read from ~/Library/Application Support/Google/Chrome/Default/Login Data which stores urls along with usernames for each

-UniversalAccessAuth --> Reads from /Library/Preferences/ to show a list of applications that the user has received authorization prompts for along with 1 (for accept) or 2 (for deny)


To run all options:


To specify certain options:

./SwiftBelt [option1] [option2] [option3]...


./SwiftBelt -SystemInfo -Clipboard -SecurityTools ...


Though this tool does not use any command line utilities (which are easy to detect), this tool does read from several files on the system which can be detected by any tools that leverage the Endpoint Security Framework (these file reads in particular are captured by ESEVENTTYPENOTIFYOPEN events within ESF).

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.