Apple Shipped Two iOS Patches and Said Nothing About the Wallet Sandbox Escape

The scariest thing about this week's iOS sandbox escape isn't the exploit. It's that Apple shipped two patched builds the next day and never said a word about it.

Here's the setup. A researcher posting as forcequitOS published a proof of concept on GitHub on Nov. 8. He called it worse_query, "a zero-day sandbox escape for iOS 26 and 27, again." It follows an earlier release of his called bad_query. The project README claims coverage from iOS 26.0 through 26.7.2, plus iOS 27.2. That's a wider net than Binance's own advisory named.

Binance warned iPhone users on Tuesday, Nov. 10, that the flaw lets a malicious app read files sitting in other apps' containers. Seed phrases. Private keys. Login credentials. The post was blunt about the scope: "This is an iOS-level issue, not unique to Binance."

What It Actually Does

On iOS, every app gets its own container. App A isn't supposed to read App B's files. worse_query breaks that wall.

SlowMist, the blockchain security firm, calls it a container sandbox escape rather than a jailbreak. That framing is correct, and it matters for how you price the risk. The bug doesn't steal anything by itself. Someone has to build it into an app, and you've to install that app from outside the App Store before anything happens.

That happened fast. Developer Christoph Kolbicz published a file manager built on worse_query one day after the release, tested on iOS 27.0.1, letting users browse and edit app data on iOS 27 without jailbreaking. So the tooling is public, packaged, and a day old.

Here's what matters: the barrier to weaponizing this dropped to roughly the effort of building an app. That's the part people are underrating.

Apple's Silent Patch

Apple shipped iOS 27.2.1 and iOS 26.7.3 on Nov. 9, exactly one day after the proof of concept went public. The security notes for both list fixes for AirPlay, Bluetooth pairing, brotli, and a handful of other components. Neither mentions worse_query. Neither describes a sandbox escape of this kind.

Maybe Apple closed it quietly. Maybe those builds were never exposed in the first place. Right now nobody outside Cupertino knows, and that ambiguity is worse than either answer would be. When a platform stays quiet, every user performs their own risk assessment, and most of them guess in the direction of "probably fine."

Binance's advisory named iOS 26.7.1, 27.0.1, and 27.2. The researcher's README claims a broader range running back to 26.0. Apple's 26.7.3 landed after that claim went up. Gap or no gap, the version math is a mess, and the people who need to act can't tell whether they're in the affected set.

Let's Argue the Other Side

The calm take isn't stupid, so let me give it a fair hearing.

SlowMist's CISO, who posts as 23pds, said the flaw won't drain assets on its own. That's true. The attack chain needs three things to line up at once: a sideloaded IPA, a user willing to install it, and a wallet that writes recovery phrases or keystores to plain files on the device. Break any one link and the chain collapses.

Hardware wallets keep keys off the phone entirely. Wallets that encrypt secrets and park them behind the Secure Enclave aren't exposed the same way. And the overwhelming majority of iPhone users never sideload anything at all. They install from the App Store, they update when nagged, and they get on with their day.

So the threat surface is narrow, multiplied by a very large population. Annoying. Not existential.

The Numbers Tell the Story

But the surrounding data complicates that comfort.

Binance is the one sending the warning, and Binance is still cleaning up from a $6.34 billion loss on Oct. 29, an attack that opened with a fake job interview. That's not a knock on their security team. It's a reminder that the entry point for most of these events isn't cryptographic. It's social. Someone talks their way in, and the math never even comes up.

And the positioning is already shifting. Large holders have been swapping self-custodied bitcoin for IBIT shares, handing custody to BlackRock's ETF wrapper instead of managing keys on their own. Ledger says an organized crime group spent millions targeting its users directly. Three separate signals, one direction: key management on consumer devices is the weakest link in the stack, and sophisticated capital has noticed.

Ask yourself this. If you had nine figures in bitcoin, would you trust it to a seed phrase sitting in an iPhone app whose sandbox just got broken in public?

My Verdict

The bug is overhyped. The patch silence is underhyped. And the custody shift it nudges along is the actual story.

I'll put conviction behind this: worse_query produces zero meaningful losses on its own. Sideloading is a sliver of iPhone behavior, and the crypto users who do it are usually the ones already running a hardware wallet. That counterpoint is real. I'm not dismissing it.

Now look at the sequence. Nov. 8, proof of concept drops. Nov. 9, a working file manager built on top of it. Nov. 9, Apple patches without disclosure. Nov. 10, an exchange with a fresh $6.34 billion hole in its balance sheet tells users to check their phones. Four days, one direction, no explanation from the platform at the center of it.

Mobile wallets are where retail custody actually lives. Every event like this pushes a few more holders toward ETFs, toward hardware, toward anything with a named human accountable for the keys. That's a slow bleed out of self-custody on phones, and frankly it's been running for a while.

If you're holding on an iPhone this week, do the boring things. Update to the newest official iOS. Delete anything you installed from a random IPA. If you've reason to think a device got touched, spin up a fresh wallet on a clean phone, move the funds, and reset every active login session. That's fifteen minutes of work against a six-figure exposure.

The exploit won't get most people.

The complacency might.