App Store downloads normally remain FairPlay-encrypted, including free apps; downloading an app does not decrypt it. An original download may only launch with its associated Apple Account/license. Re-signing requires a self-built, DRM-free, or lawfully decrypted IPA (see Security Testing).
Demo
Download
|
Re-sign IPA
|
Install to Device
|
Switch Account
|
Change Storefront
|
Installation
brew install --cask ipaverse
Or build from source:
git clone https://github.com/bahattinkoc/ipaverse.git
cd ipaverse
open ipaverse/ipaverse.xcodeproj
Requirements and device-install notes:
- Apple Silicon Mac (
arm64) running macOS 14.6 (Sonoma) or later.
- Building from source requires Xcode; the latest stable release is recommended.
- Device installation targets iPhone and iPad. The CoreDevice path uses Xcode’s
xcrun devicectl; a bundled libimobiledevice fallback supports older devices over USB.
- Wi-Fi installation requires the device to be paired over USB first and Connect via network to be enabled in Xcode’s Devices window.
Features
- Search the iOS, iPadOS, macOS, tvOS, and visionOS App Store catalogs and download available packages. ipaverse can acquire licenses for free apps; paid apps must already be licensed to the active Apple Account.
- Manage multiple Apple ID accounts, switch storefronts/regions, and browse version history.
- Use the library offline; group versions and original, imported, re-signed and decrypted copies, with source filters and missing-file recovery.
- Queue individual versions or multiple apps, track two concurrent downloads, and retry interrupted jobs after restarting.
- Compare IPA copies with matching bundle IDs: metadata, entitlements, signing, Mach-O, components, resources and findings, with A/B and line diffs. Optional deep analysis adds symbols, classes, strings and endpoint candidates; export full or filtered JSON.
- Edit IPA properties/files and re-sign DRM-free IPAs with your own certificate and provisioning profile, including from a standalone Resign window.
- Review signing profiles, extension identities, and device readiness before signing or installing compatible IPAs on an iPhone or iPad over USB or Wi-Fi.
- Run local static analysis, browse Objective-C classes, and use an authorized live Frida toolkit; manage optional external analysis tools from Settings.
Full usage guide, screen by screen → USAGE.md
Security Testing
ipaverse includes a toolkit aimed at security researchers doing authorized iOS app testing: a Security Testing Mode toggle (disables ATS for MITM proxying), Frida Gadget injection, a Dump Decrypted Copy tool for FairPlay apps on a jailbroken source device, and Reverse Engineer — local static analysis, an Objective-C class browser, and live Frida tools for bypasses, method tracing, NSURLSession interception, UI hierarchy inspection, and app-data inspection.
In the data tools, NSUserDefaults string/number values are editable; Keychain output is limited to item metadata, and matching sandbox files can be listed and downloaded. These features — plus Move to New Identity in the Re-sign window — stay disabled until you turn on Evil Mode from the main toolbar. Evil Mode is a deliberate UI guardrail, not a substitute for authorization.
Frida Gadget and libfrida-core are not bundled in the app. They are downloaded from this repository’s GitHub Releases on first use, checked against pinned file sizes and SHA-256 digests, and cached in Application Support. Dumping a decrypted copy requires a jailbroken USB device with frida-server running and the target app open. Details and live-tool prerequisites → USAGE.md § Security Testing.
⚠️ Educational and authorized use only. These tools are meant for bug bounty programs, contracted pentests, or testing apps you own. Do not use them against apps, accounts, or systems you don’t have explicit permission to test — misuse may violate Apple’s terms of service and/or the law. ipaverse and its author take no responsibility for misuse.
Security & Privacy
ipaverse is local-first, but it is not an offline application:
- Authentication, App Store search/license/download requests, artwork loading, and the initial SAP asset fetch communicate directly with Apple services.
- Authentication uses Apple’s GrandSlam SRP-6a flow. The raw password is used locally to produce the SRP proof and is not sent directly. By default, ipaverse tries macOS’s AOSKit first and automatically uses an Anisette V3 service if local generation fails, including on affected macOS 27 betas. The login screen explains this service use. Remote generation sends a generated device identity and provisioning data, never Apple Account credentials or verification codes. The default service is operated by SideStore. Settings → Account → Advanced Sign-in Settings lets you restrict generation to this Mac or configure your own server; existing choices are preserved. See Anisette sign-in options.
- Account/session credentials are stored in macOS Keychain. A password is retained for quick login only when Remember Me is enabled; non-secret profile metadata and preferences are stored in UserDefaults.
- IPA extraction, patching, signing, static analysis, report generation, and security-test data processing happen locally. Certificates, provisioning profiles, and IPA contents are not uploaded by ipaverse.
- GitHub is contacted only for an explicit update check and for on-demand Frida downloads. Installing optional tools contacts Homebrew, pip, or the selected vendor site. These requests do not include Apple credentials, certificates, profiles, or IPA contents.
- The project has no project-operated authentication relay, analytics service, or telemetry backend.
Please report vulnerabilities privately as described in SECURITY.md.
License
The original ipaverse source code in this repository is provided under the MIT License. Distributed builds also contain or load third-party components whose own license terms continue to apply; the app as distributed should not be described as MIT-only.
Notable components include:
bahattinkoc/ipaverse
评论