SuperAPI AI Directory

macos-reverse

General & other

View repository

Updated 10-16 09:45

About this skill

macOS / Mach-O Reverse Engineering

ACTION REQUIRED (execute immediately after reading)

  1. NOW: Read ../field-journal/precedent-reverse.md
  2. NOW: Confirm target is macOS/Mach-O/App bundle (iOS IPA → mobile-reverse/)
  3. NEXT: tool-index; jtool2/lldb etc.
  4. ACT: Signing and loading information → static → dynamic (lldb/Frida)

Applicable scenarios

  • Mach-O executable / dylib / framework
  • .app bundle、LaunchAgent/Daemon
  • Objective-C / Swift symbols and runtime
  • Notarization/signing, Hardened Runtime, TCC-related behavior analysis
  • macOS malware static/dynamic analysis (combined with malware-analysis)

Workflow

1. Bundle and signing

file target
codesign -dv --verbose=4 target
spctl -a -vv target 2>&1
otool -L target

2. Static

□ class-dump / swift-demangle / Hopper / Ghidra / IDA
□ 字符串与 XPC 服务名、TCC 敏感 API
□ LC_LOAD_dylib 依赖与 rpath

3. Dynamic

□ lldb / Frida
□ fs_usage / log stream 观察
□ 网络:联合 protocol-reverse 或代理

Toolchain

Tool Purpose
otool / nm / codesign Built-in
Hopper / Ghidra / IDA Decompilation
class-dump / dsdump ObjC
Frida / lldb Dynamic
jtool2 Mach-O

References

  • references/macho-triage.md
  • ../mobile-reverse/(iOS) ../ghidra-reverse/ ../malware-analysis/

Routing context

Upstream: MASTER R31
Downstream: iOS → mobile-reverse; general samples → malware-analysis

Task completion self-check

  • Is the signing/Hardened Runtime status recorded?
  • Are there address-level/symbol-level conclusions?
  • Checklist?