AirCard: Custom Apple Wallet Card Skins and Lockscreen Passcode Themes on iOS 18+ Without a Jailbreak
Apple Wallet Card Skinner for iOS 18+ (No Jailbreak Required)
At a glance
- What is it?
- AirCard is a macOS app that skins Apple Wallet cards and applies .passthm lockscreen passcode themes to iOS 18+ devices over USB, using the airlift AirTraffic sync escape. It is aimed at people already comfortable with sideloading and Gatekeeper prompts, not at casual users.
- Who is it for?
- AirCard suits Mac owners who already accept Gatekeeper workarounds and want per-card Wallet artwork or .passthm passcode themes on iOS 18+ without jailbreaking. It is the wrong tool for anyone on Windows or Android, and for users who cannot tolerate force-closing Wallet or rebooting the iPhone after flashing.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 41 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Mak5er/AirCard7,135 ★ · +1,968
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| Mak5er/AirCard | 5.2k | 7.1k |
1,968 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What AirCard changes, and the users it is built for
AirCard assigns custom artwork to individual Apple Pay and Wallet cards, and it applies lockscreen passcode button themes in the .passthm format to iOS 18+ devices. Both jobs happen from a Mac over a USB connection. The README states support for iOS 18.0 through 27.0.1 and iOS 27.2 beta 1 and 2, marks iOS 27.2 beta 3 and newer as patched, and requires no jailbreak.
The second half of the tool is arguably the more interesting one. AirCard can open an existing Cowabunga or Nugget theme package, let you adjust button artwork, reposition photos inside the keypad buttons, and then re-export or flash it. There is also a creator that builds a theme from a single wallpaper through what the README calls Seamless Poster Slicing, or key by key through Individual Keys.
This is not a tool for a general iPhone owner. It assumes a Mac, a USB cable, an unlocked and trusted device, and a willingness to right-click past a Gatekeeper prompt. The README is explicit that macOS users need no Homebrew, Python packages or terminal setup, and that device-communication utilities and image engines are bundled inside the app. That packaging is what makes the audience wider than the usual exploit-tool crowd, but the workflow still ends with force-closing Wallet or restarting the iPhone.
How AirCard talks to the iPhone: airlift, MobileDevice and the unified log
The mechanism is visible in the repository layout and the Makefile. Two native helpers are compiled: build/device_helper links against Foundation, CoreFoundation and the private MobileDevice framework, while build/airtraffic_host links against AirTrafficHost. Both are built with -fobjc-arc and ad-hoc signed with codesign --force --sign -. The Makefile builds universal binaries for arm64 and x86_64.
The README says AirCard is powered by the airlift AirTraffic sync exploit. AirCard is the front end over that escape, not a reimplementation of it.
Card detection works differently from flashing. The README says the scanner reads the iPhone's unified log service, including Info and Debug events, which is why the instructions ask you to open Apple Pay, authenticate with Face ID, and tap a card to trigger detection. That is also the source of the tool's most documented failure: on iOS 18.6.2 the legacy log service can show Wallet activity while omitting the resource lookup messages that carry card identifiers. Values iOS replaces with <private> are not recoverable by the scanner, according to the README. A log line reading Connected to the unified device log stream is the signal that the reader is attached.
The repository also contains aircard.py, aircard_backend.py, apply_card_skin.py and card_assets.py alongside the Swift app entry point.
Installing AirCard from the DMG and flashing a first card skin
The README points macOS users at the AirCard.dmg asset on the Releases page. Drag AirCard.app into Applications. If macOS shows an unidentified developer prompt on first launch, either right-click the app and choose Open, or clear the quarantine attribute from a terminal:
sudo xattr -cr /Applications/AirCard.appThe README lists this as a first-launch Gatekeeper workaround. After that, connect the iPhone by USB, unlock it, and trust the computer.
With the device attached, open the Wallet Cards tab and click Scan Cards. The README's sequence is: double-click the side button to open Apple Pay, authenticate with Face ID, then tap your card to trigger detection. The Log view should show the connection line before the taps register. Once a card appears, drop an image onto the card mockup or click the card and pick artwork, then click Flash Skins. The README says you must force-close the Wallet app from the App Switcher, or reboot, before the new design shows.
Building from source instead of using the DMG goes through the repository's build.sh script:
git clone https://github.com/mak5er/AirCard.git
cd AirCard
chmod +x build.sh
./build.shThe Makefile compiles the native helpers as universal arm64 and x86_64 binaries. The Makefile targets are build/device_helper and build/airtraffic_host, so the build depends on the private MobileDevice and AirTrafficHost frameworks present on the host Mac.
Applying a .passthm passcode theme, and why a restart is mandatory
Switch to the Passcode Themes tab and drag a .passthm file into the window, or click Choose .passthm File. AirCard then inspects the theme.
Where AirCard fails: private log values, scanner coverage and platform limits
The most concrete limitation is documented by the project itself. Card detection depends on resource lookup messages in the unified log, and the README notes that on iOS 18.6.2 the legacy log service can show Wallet activity while omitting exactly those messages. When that happens, Scan Cards returns nothing even though the phone is connected and Apple Pay is open. The README also states that values iOS replaces with <private> cannot be recovered by the scanner. The README does describe a partial fallback: once a live ID matches one specific remote-device cache, the remaining payment IDs from that cache are included so cards omitted by iOS logging still appear.
A second limitation is that force-closing Wallet or rebooting the iPhone is part of the documented card-skin procedure, not an optional step, so this is not a tool for someone who wants to preview a skin and keep using the phone uninterrupted.
The platform boundary is absolute. Despite the name, this AirCard has nothing to do with the Netgear or Sierra Wireless hotspots or the Rolling Square tracker. The README describes a macOS-only app that talks to an iPhone over USB. There is no official Windows build (the README points Windows users to an unofficial port, AirCard-Windows), no Android support and no self-hosted server component.
Finally, the README asks users who hit a zero-card scan to report their iPhone model, iOS version, macOS version and AirCard version or commit, while warning against posting full device logs or card identifiers. That request implies scanner coverage is still incomplete for some device and OS combinations, and docs/wallet-card-detection.md is the place the README points to for the verified environment.
AirCard compared with Cowabunga and Nugget theme workflows
The only other tools the README names are Cowabunga and Nugget. AirCard opens .passthm packages produced by those tools, which means it is designed to sit alongside them rather than replace them. AirCard does the theme editing and the flashing in a Mac app with a real-time iPhone preview and per-button photo framing, and then pushes the result over USB.
That split has consequences. You get a larger editing surface and a real preview, but you add a cable and a trusted-computer pairing to every iteration. AirCard also handles Wallet card artwork, which the theme tools are not described as doing.
On the exploit side, AirCard depends on airlift rather than shipping its own escape. That is a reasonable division, and it also means AirCard's compatibility window is tied to whatever airlift supports on a given iOS release. The README already marks iOS 27.2 beta 3 and newer as patched, where flashing will not work.
Licence, maintenance and what an upgrade actually costs you
AirCard is MIT licensed, which permits commercial and private use, modification and redistribution provided the copyright notice and permission notice are retained. The repository includes the LICENSE file. Nothing here is legal advice.
Maintenance looks current. The last push was on 2026-10-05, and the latest release is v1.2.6 (2026-10-04), a hotfix for card discovery and cache invalidation, following v1.2.5 on 2026-09-30 and v1.2.4 on 2026-09-22. The repository is not archived.
Upgrade cost is dominated by iOS, not by AirCard. Each iOS release can change the unified log behaviour the scanner relies on, as the iOS 18.6.2 note shows, and it can also change whether the underlying airlift escape still works. Budget for re-verifying card detection after every iOS update, and read the release notes before assuming a new AirCard build covers your OS. The macOS side is comparatively stable, since the DMG is universal and bundles its dependencies.
Editorial conclusion
AirCard suits Mac owners who already accept Gatekeeper workarounds and want per-card Wallet artwork or .passthm passcode themes on iOS 18+ without jailbreaking. It is the wrong tool for anyone on Windows or Android, and for users who cannot tolerate force-closing Wallet or rebooting the iPhone after flashing. Before adopting it, verify your iPhone model and iOS version against docs/wallet-card-detection.md, confirm the Scan Cards step actually finds your cards, and check whether your device's unified log replaces card identifiers with <private>, because the README states those values cannot be recovered.
Frequently asked questions
What does AirCard do?
It assigns custom artwork to Apple Pay and Wallet cards and applies .passthm lockscreen passcode themes on iOS 18+ devices, working from a Mac over USB. The README states no jailbreak is required.
How do I install AirCard on macOS?
Download AirCard.dmg from the Releases page and drag AirCard.app into Applications. If macOS shows an unidentified developer prompt, right-click the app and choose Open, or run sudo xattr -cr /Applications/AirCard.app.
Do I need Homebrew or Python to use AirCard?
No. The README states macOS users need no Homebrew, Python packages or terminal setup, because the device-communication utilities and image engines are bundled inside the app. AirCard does use the macOS native Python 3 (/usr/bin/python3), and if macOS asks for Developer Tools the README says to run xcode-select --install.
Why does Scan Cards find no cards in AirCard?
The scanner reads the iPhone's unified log, and the README notes that on iOS 18.6.2 the legacy log service can show Wallet activity while omitting the resource lookup messages containing card identifiers. Values iOS replaces with <private> cannot be recovered by the scanner.
What is an Apple AirCard?
In this repository, AirCard is an open source macOS app for skinning Apple Wallet cards and applying lockscreen passcode themes on iOS 18+. It is unrelated to the Netgear and Sierra Wireless hotspot products that also use the AirCard name.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 0 in the last 30 days; newest first.
- AirCard: Customize Apple Pay card artwork without a jailbreakHacker News · Sep 27, 2026 · 1 points · 0 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/mak5er-aircard)Star history chart for your README
[](https://hysenlabs.com/projects/mak5er-aircard)Was this useful?