Individual skill

reverse-eng-macos

Reverse macOS Mach-O binaries and .app bundles — codesign/notarization state, entitlements, Objective-C/Swift symbol recovery, and lldb/Frida dynamic analysis. Load when the target is a Mach-O executable/dylib/framework, an .app bundle, a LaunchAgent/Daemon plist, or Apple-platform malware. Signals: "Mach-O 64-bit executable", codesign/spctl output, hardened runtime, objc_msgSend, mangled _ZN/_$s symbols, XPC service names, TCC prompts.

skills/reverse-engineering/reverse-eng-macos/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# macOS / Mach-O reversing

## When it applies
The target is a Mach-O binary, dylib, framework, or `.app` bundle on macOS (or a sample you can
read offline), and it is in scope (`tradecraft-scope-roe`, `scope.txt`). iOS IPAs are a different
surface — treat them with the iOS assessment flow (`mobile-ios-assessment`). Typical jobs:
understand a thick client, audit a persistence item (LaunchAgent/Daemon), or analyze Apple-platform
malware.

## Why it works
Mach-O carries its trust model in-band: the code signature, entitlements, and load commands say
what the binary may do before you read a single instruction. Objective-C keeps class and selector
names in `__objc_*` sections and Swift symbols demangle to full signatures, so static recovery is
cheap — and Apple's own tools (`codesign`, `otool`, `lldb`, `log`) cover most of the workflow.
Back to top