dylex
A high-performance dyld shared cache extractor for macOS and iOS, written in Rust.
dylex extracts Mach-O files for static analysis from Apple's dyld shared cache, with symbol table reconstruction, pointer decoding, and LINKEDIT rebuilding. Extraction does not reconstruct a runnable OS loader environment.
Features
- Fast Extraction - Memory-mapped I/O and parallel processing for maximum speed
- Automatic Cache Discovery - Finds system caches automatically on macOS
- Architecture Selection - Support for arm64, arm64e, and x86_64 caches
- Symbol Table Reconstruction - Rebuilds standalone LINKEDIT with proper symbol tables
- Pointer Rebasing - Handles slide info v3/v5 for correct pointer values
- ObjC Metadata Restoration - Reconstructs coalesced strings and absolute method entries before clearing encoding flags
- Cache Islands - Retains referenced sectionless ARM64 stubs and
libobjcMsgSend*dispatcher code - Rosetta Cache Products - Discovers native, full Rosetta, and reduced
x86Supporttrees separately - Directory Structure Preservation - Optionally preserves full framework paths
- Batch Extraction - Extract multiple images with filters and parallel processing
See cache compatibility and validation for the tested macOS 27 build, older-format fixtures, source provenance, assumptions, and mode limitations.
Installation
From crates.io
From Source
GitHub Actions binaries
The macOS build workflow tests and builds
Intel (x86_64) and Apple Silicon (arm64) binaries on pushes, pull requests,
and manual runs. Download dylex-x86_64-apple-darwin or
dylex-aarch64-apple-darwin from the run's artifacts. Each contains a .tar.gz
with the executable and license, plus a SHA-256 checksum file.
See CI build details for runner selection and validation scope.
Quick Start
# List available architectures in the system cache
# Show cache information
# List all images containing "UIKit"
# Extract a single library
# Extract all MapKit-related frameworks with preserved paths
Commands
dylex extract
Extract images from the dyld shared cache.
Usage: dylex extract [OPTIONS] [CACHE]
Arguments:
[CACHE] Path to the dyld shared cache (file or directory).
If not specified, searches default system locations.
Options:
-i, --image <IMAGE> Image to extract (e.g., "UIKit" or full path)
-f, --filter <FILTER> Filter images by substring match
-a, --arch <ARCH> Architecture (arm64e, arm64, x86_64)
-o, --output <OUTPUT> Output path (file or directory)
--merge-image <IMAGE> Merge a selected additional image (repeatable)
--merge-runtime Merge directly referenced runtime libraries
--merge-plan Preview merge selection and reference evidence
--merge-deps Experimental automatic dependency merge
--merge-depth <N> Depth for --merge-deps [default: 1]
--preserve-paths <BOOL> Preserve directory structure [default: auto]
-v, --verbosity <LEVEL> Verbosity (0=quiet, 1=warn, 2=info, 3=debug)
-j, --jobs <N> Parallel jobs (default: CPU count)
-h, --help Print help
Examples
# Extract single image to specific file
# Extract by full path
# Extract all Foundation-related images
# Extract everything (warning: large!)
# Extract with verbose output
# Use custom cache path
Merge referenced runtime libraries
# Inspect which runtime images are referenced and where
# Merge the inferred runtime set
# Add an explicit framework to the roots used for runtime inference
--merge-runtime selects directly referenced libraries in /usr/lib/system/,
Objective-C, libc++, libc++abi, libSystem, and /usr/lib/swift/libswift*.dylib.
It scans ARM64 direct branches and declared pointer sections, resolves recognized
stubs, and reports reference counts with an example source/target chain for each
inferred image. The primary and explicit additions are scan roots. Inferred
libraries are not scanned recursively; dependency lists do not drive selection.
Frameworks and other libraries remain explicit additions.
--merge-plan writes no output. Computed calls without static pointer evidence
are unknown; x86 inference uses pointer sections rather than instruction decoding.
On the tested cache, GeoServicesCore selects ten runtime libraries. Empty section
markers left by cache optimization are omitted unless a symbol references them.
All populated sections are retained regardless of count. Because nlist n_sect
is 8 bits, a symbol in a section past ordinal 255 carries the ordinal of an
earlier section of the same kind; its address stays exact. Adding GeoServices
as a root infers 29 runtime images and merges 31 images into 724 sections.
Merge selected images
Use --merge-image once per additional image. This selects the primary image
and the listed images without traversing their dependency lists:
Image selection prefers a full path, then an exact basename, then a unique
substring. Ambiguous names produce an error listing candidate paths. Repeated
images are included once, and the command prints the canonical selection.
--merge-image and --merge-runtime cannot be combined with --merge-deps, --merge-depth,
--with-deps, or --filter.
The output keeps source virtual addresses and instruction bytes. It combines sections, symbols, indirect-symbol tables, and function-start labels; referenced cache trampolines/dispatchers and Objective-C metadata are restored for the combined image. Those support regions can make output substantially larger than the selected images' own segments. External targets outside the selection can remain unmapped. These outputs are for static analysis; runtime loading is not supported. Open the newly extracted file in a fresh IDA database.
See selected-merge validation for tested behavior and
format limits. The automatic --merge-deps mode retains its older experimental
relocation pipeline.
dylex list
List images in the cache.
Usage: dylex list [OPTIONS] [CACHE]
Options:
-a, --arch <ARCH> Architecture to use
-f, --filter <FILTER> Filter images by name
-A, --addresses Show virtual addresses
-b, --basenames Show only basenames (not full paths)
-h, --help Print help
Examples
# List all images
# List with addresses
# Filter and show basenames
# Count images matching filter
|
dylex info
Display detailed cache information.
Usage: dylex info [OPTIONS] [CACHE]
Options:
-a, --arch <ARCH> Architecture to use
-h, --help Print help
Example Output
Dyld Shared Cache Information
==============================
Path: /System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld/dyld_shared_cache_arm64e
Architecture: arm64e
Images: 3554
Mappings: 22
Subcaches: 2
Total size: 5307.38 MB
Mappings:
[ 0] 0x0000000180000000 - 0x00000001e6660000 ( 1.6G) r-x
[ 1] 0x00000001e6660000 - 0x00000001e8874000 ( 34.1M) r-- [slide]
...
Subcaches:
[ 1] dyld_shared_cache_arm64e.01 (2543.53 MB)
[ 2] dyld_shared_cache_arm64e.02 (196.12 MB)
dylex arches
List available cache architectures.
Usage: dylex arches [PATH]
Arguments:
[PATH] Directory to search. If not specified, uses system default.
Example Output
Available architectures in /System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld:
arm64e - dyld_shared_cache_arm64e
x86_64 - dyld_shared_cache_x86_64
dylex lookup
Find which image contains a specific unslid cache address. Cache-owned ARM64
stub islands are followed to their target image (up to 64 hops, with cycle
detection). Output includes the image path, segment, exact symbol or nearest
preceding symbol, an extraction command using the same cache, and a
--merge-image option. A nearest symbol does not establish function extent.
For the cache used in this validation:
0x2480895f0 → 0x1806cf570 → /usr/lib/system/libdispatch.dylib
Symbol: _dispatch_once
0x2480896b0 → 0x180410d48 → /usr/lib/libobjc.A.dylib
Symbol: _objc_retainAutoreleaseReturnValue
Addresses vary between cache builds.
Usage: dylex lookup [OPTIONS] <ADDRESS> [CACHE]
Arguments:
<ADDRESS> Address to lookup (hex, e.g., 0x180000000)
Options:
-a, --arch <ARCH> Architecture to use
-h, --help Print help
Default Cache Locations
When no cache path is specified, dylex searches these locations in order:
/System/Volumes/Preboot/Cryptexes(native OS and Rosetta products)/System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld/System/Library/dyld/var/db/dyld
Commands without --arch retain the native system-cache default. dylex arches
lists each product separately. When --arch x86 matches both Rosetta caches, an
exact main-file path selects the product:
These Rosetta paths were observed on macOS 27 build 26A5425a. Discovery excludes
staged Incoming updates and DriverKit subtrees unless selected explicitly.
Architecture Selection
The --arch flag uses substring matching:
| Flag | Matches |
|---|---|
-a arm64e |
arm64e only |
-a arm64 |
arm64 and arm64e |
-a x86 |
x86_64 and x86_64h |
If multiple architectures match, you'll be prompted to be more specific.
Output Structure
Single Image Extraction
By default, single images are extracted to the current directory with their basename:
# Creates: ./libobjc.A.dylib
Batch Extraction with Filter
When using -f/--filter, directory structure is preserved by default:
# Creates:
# ./extracted/System/Library/Frameworks/MapKit.framework/Versions/A/MapKit
# ./extracted/System/Library/Frameworks/_MapKit_SwiftUI.framework/Versions/A/_MapKit_SwiftUI
# ./extracted/usr/lib/swift/libswiftMapKit.dylib
# ...
Use --preserve-paths false to flatten:
# Creates:
# ./flat/MapKit
# ./flat/_MapKit_SwiftUI
# ./flat/libswiftMapKit.dylib
What dylex Does
When extracting an image, dylex performs these operations:
- Copies Segment Data - Extracts __TEXT, __DATA, __LINKEDIT, etc.
- Rebases Pointers - Applies slide info to fix pointer values
- Rebuilds LINKEDIT - Creates standalone symbol table, string table, and other metadata (replaces ~600MB shared LINKEDIT)
- Fixes ObjC Metadata - Clears
OBJC_IMAGE_OPTIMIZED_BY_DYLDflag - Updates Load Commands - Adjusts offsets for standalone operation
- Optimizes File Layout - Removes unnecessary padding
Library Usage
dylex can be used as a library:
use ;
Performance
dylex is designed for speed:
- Memory-mapped I/O - No unnecessary copying
- Parallel extraction - Uses all CPU cores for batch operations
- Efficient data structures - FxHashMap for fast lookups
- LTO-optimized release builds - Maximum binary performance
Typical extraction times on Apple M1:
- Single library: ~0.3s
- 100 libraries: ~5s
- Full cache (~3500 images): ~3-5 minutes
Limitations
- macOS/iOS only - dyld caches are Apple-specific
- Read-only - Cannot modify or repack caches
- No code signing - Extracted binaries need re-signing for execution
- External references - Ordinary inter-library targets can remain external
- Analysis layout - Images with insufficient header padding use a separate
__DYLEX_HDRsegment; original code addresses remain unchanged - Unknown extensions - Version-4 ObjC optimization fields after the common prefix are not interpreted as version-2 buffer sizes
- Merged extraction -
--merge-imagesupports explicit selection at cache addresses, with at most 255 retained symbol sections after removing unused empty markers.--merge-depsretains its separate experimental relocation pipeline
Comparison with Other Tools
| Feature | dylex | dsc_extractor | DyldExtractor |
|---|---|---|---|
| Language | Rust | C++ | Python |
| Speed | Fast | Medium | Slow |
| LINKEDIT rebuild | Yes | Partial | Yes |
| Slide info v5 | Yes | Yes | Yes |
| Parallel extraction | Yes | No | No |
| Library API | Yes | No | Yes |
Troubleshooting
"No dyld shared caches found"
The default cache locations may not exist on your system. Specify the path explicitly:
"Multiple caches match"
Be more specific with the architecture:
# Instead of -a arm64 (matches arm64 and arm64e)
Extracted binary won't run
Extraction produces files for static analysis. Code signing alone does not restore bind/rebase metadata, cache-wide runtime state, or unresolved external references.
Large extracted file sizes
Some libraries (like libobjc) include large shared ObjC metadata segments. This is expected behavior.
Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
License
MIT License - see LICENSE for details.
Acknowledgments
- Inspired by DyldExtractor
- Apple's dyld source code for format documentation
- The reverse engineering community