OneKey maintainer Yishi is urging users who rely on an offline iPhone as a cryptocurrency signing device to treat physical compromise—not internet connectivity—as the central security risk. His recommended baseline is an iPhone 17 or newer running iOS 27 or later with current patches, a strong passcode, separate wallet protections, and replacement hardware every one to two years.
The guidance challenges the common assumption that a phone becomes a secure “cold wallet” simply by disabling wi‑fi, bluetooth, and cellular access. An offline handset can still contain recovery phrases, wallet files, screenshots, notes, cached data, and cryptographic keys that may be exposed if somebody obtains the device and can inspect it, exploit it locally, or compel its owner to unlock it.
Yishi’s framework places more weight on the phone’s hardware generation, operating-system patch level, lock state, passcode strength, and wallet architecture. Network isolation remains useful, but it does not erase data already stored on the handset or close wired attack paths.
Border searches show the limits of offline protection
The issue is especially relevant for travelers. U.S. Customs and Border Protection recorded 55,318 electronic-device searches during fiscal 2025, including 50,922 basic searches and 4,396 advanced searches, according to the agency’s annual report. The fiscal year ran from Oct. 1, 2024, through Sept. 30, 2025.
Under CBP policy, a basic search generally consists of reviewing material displayed on the device screen. An advanced search uses external equipment, whether wired or wireless, to copy or analyze the contents of an electronic device. A January 2026 CBP directive says that requiring a traveler to make content available for inspection—such as by entering a passcode—does not alone turn a search into an advanced examination.
CBP policy also instructs officers to focus on data stored locally and to disable network connectivity, or ask the traveler to do so, to avoid accessing cloud-only content. That practice undercuts the notion that offline mode prevents inspection. A device can be isolated from networks and remain fully capable of displaying locally saved seed phrases, screenshots, photos, documents, or decrypted wallet information.
A recovery phrase stored in photos, notes, or a screenshot remains a direct exposure if the phone is unlocked. Apple’s hidden and recently deleted photo albums are protected by Face ID, Touch ID, or a passcode, but deleted images generally remain in recently deleted for 30 days. Locked notes can use either the device passcode or a separate password; Apple also says that after one locked note is opened, other locked notes in the same account can be accessible for several minutes.
Lock state can change forensic exposure
Yishi’s advice to power down a dedicated signing phone after use rests on the difference between BFU and AFU states. BFU means “before first unlock,” the condition after an iPhone reboots and before its passcode has been entered. AFU, or “after first unlock,” begins once the phone has been unlocked after boot and can persist after the screen is locked again.
Apple’s data protection system uses per-file encryption keys and several protection classes. Apple states that files using the NSFileProtectionCompleteUntilFirstUserAuthentication class can remain available after the phone has been unlocked once, because the relevant class key stays in memory after a subsequent lock. More restrictive file-protection classes discard decrypted class keys when the device locks.
The practical effect depends on how a specific wallet stores secrets. A wallet may use stricter file protection, keychain controls, an additional encryption layer, or hardware-backed authorization. AFU status therefore does not prove that a recovery phrase or private key can be read, but it can expand the data available to a capable local attacker compared with a freshly rebooted phone.
Apple introduced an inactivity reboot function in iOS 18. Security researcher Jiska Classen documented a 72-hour reboot interval in tested builds, while describing an earlier seven-day interval. Classen said the timing appeared to be tracked by the secure enclave processor rather than a conventional iOS background timer. A normal reboot returns an iPhone to BFU and clears some decrypted state, which is why Yishi recommends turning off a storage device rather than merely locking it.
Forensic firms continue to target this distinction. Cellebrite’s spring 2026 release material said its advanced services supported AFU access for iPhone 11 through iPhone 16 models running iOS 26 or later. The same material referred to iPhone 17 and iOS 26.3.1, while providing limited public detail on support for the newest devices. Cellebrite also said 75% of devices received by North American forensic labs were locked, a figure describing the condition of phones at intake rather than the company’s success rate in accessing them.
Newer iPhones add hardware defenses older models cannot receive
Yishi’s iPhone 17 floor is tied to Apple’s A19-generation security architecture. Apple says its memory integrity enforcement, or MIE, system uses typed allocators, enhanced memory tagging extension technology, and tag confidentiality to make memory-corruption attacks more difficult. The company said MIE operates in the kernel and in more than 70 user-space processes.
Those protections require hardware support. Apple has said older devices cannot receive the missing enhanced memory tagging extension capabilities through a software update. An older phone can remain patched against known iOS vulnerabilities, but it cannot gain the same underlying defenses by installing a newer operating system.
Devices based on Apple’s A5 through A11 chips carry another long-term disadvantage: the checkm8 BootROM vulnerability. The flaw affects models including the iPhone X and cannot be removed through a normal iOS update because the BootROM is fixed in hardware. A boot-chain compromise does not automatically decrypt an iPhone’s user data or defeat the secure enclave, but it gives attackers a durable foothold unavailable on later hardware.
Recent disclosures also illustrate why software version remains central. Google’s 2026 Coruna research detailed five iOS exploit chains involving 23 vulnerabilities, while Google’s DarkSword research described payloads designed to collect cryptocurrency wallet data on vulnerable iOS versions. In both cases, patches were available for the affected ranges. Keeping a phone offline would not undo a compromise that occurred before it was disconnected.
Passcodes and wallet design determine the damage from access
Apple ties passcode-derived encryption to a unique hardware UID and says each passcode attempt is calibrated to take roughly 80 milliseconds, before increasing delays and attempt limits are considered. The UID is not exposed through JTAG or standard debugging interfaces, according to Apple, limiting the value of simply copying a device’s flash storage for mass offline password guessing.
Using Yishi’s simplified assumption that attempt limits have somehow been bypassed but guesses remain sequential at 80 milliseconds each, exhausting a random six-digit numeric passcode would take about 22.2 hours, with an average discovery time of about 11.1 hours. A 10-character random lowercase alphanumeric passcode would require about 9.27 million years across the full search space under the same assumptions. A 12-character random mixed-case alphanumeric passcode would take roughly 8.18 trillion years.
Those calculations do not make a phone invulnerable. They show why a short numeric code gives attackers a far more realistic path than a long, randomly generated passcode. Yishi recommends a 12-character random alphanumeric device passcode rather than a conventional six-digit PIN.
A wallet’s own key-management design provides another layer. Wallet software can encrypt recovery material, use hardware-protected keys, or restrict access through keychain policies such as whenunlocked and whenpasscodesetthisdeviceonly. The latter option limits syncing and backups while tying access to a device with a passcode configured.
Apple’s secure enclave can generate P-256 keys without exposing their private material, but Bitcoin and Ethereum typically use the secp256k1 curve. That technical mismatch means a wallet cannot necessarily place every signing key directly inside the secure enclave using Apple’s standard key APIs. Developers may instead use hardware-backed keys to wrap an encrypted seed or wallet-encryption key.
That design can reduce exposure, though it also shifts attention to authorization flows and the app’s runtime environment. A wallet protected only by a separate password derived with PBKDF2 or Argon2 could face offline guessing if an attacker obtains its encrypted data, salt, and configuration without any additional device-bound secret.
A dedicated phone needs operational discipline
Yishi’s approach calls for a dedicated, unjailbroken phone with no unrelated apps, reduced lock-screen controls and accessory access, and wi‑fi and bluetooth disabled in settings rather than only disconnected through control center. The distinction matters because control center can preserve radios or allow them to reconnect under certain conditions, while settings provides a more direct configuration change.
Apple’s USB restricted mode is designed to limit wired data access on locked devices, yet Apple’s advisory for CVE-2025-24200 said a physical attack could disable that protection on a locked device. Apple fixed the flaw in iOS 18.3.1 and said it may have been used in an “extremely sophisticated” attack against specific targets.
The recommended setup also avoids storing recovery phrases in notes, photos, screenshots, or cloud-backed files. Offline paper or metal backups, tested through a recovery procedure before substantial funds are transferred, remove the most direct route from a seized handset to a wallet’s master secret.
An iPhone can serve as part of a carefully designed signing arrangement, but its security depends on more than keeping it disconnected. Current hardware, current patches, a cold boot before storage, a strong passcode, and wallet protections independent of Face ID together make physical access materially harder to turn into access to cryptocurrency funds.
For more on securing your coins beyond device choice, explore our guide on cold vs hot wallets and practical protection steps.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
