# Worse Query iOS flaw: how to protect your crypto wallet

> A public iOS sandbox escape called Worse Query can expose other apps' data. Here is how to check, contain and recover.

- Published: 2026-11-12
- Topic: [Security](https://futuretechnologyhq.com/topic/security/)
- URL: https://futuretechnologyhq.com/article/worse-query-ios-flaw-how-to-protect-your-crypto-wallet/
- Publisher: [Future Technology HQ](https://futuretechnologyhq.com/), free to read. Quote as "Future Technology HQ" with a link to the article.

## Key points

- Worse Query needs no jailbreak or kernel exploit and a working proof-of-concept is public
- Apple's iOS 27.2.1 release notes did not mention the sandbox escape
- Move funds to a new wallet created on a clean device and reset all login sessions if you suspect a breach

## Article

After reading this, an IT team or an individual crypto holder will be able to assess whether an iPhone is exposed to the Worse Query sandbox escape, reduce the attack surface, and recover safely if a wallet may have been compromised. Difficulty: moderate. Time: longer for a managed fleet than for a personal device.

The background is short. Worse Query, disclosed by the researcher behind its predecessor Bad Query, which dates from August, lets a malicious app read other apps' private data without a jailbreak or kernel exploit. It affects iOS 26.7.1, 27.0.1 and 27.2. A working proof-of-concept went public on Monday. Apple shipped iOS 27.2.1 the same day, but the release notes did not mention the sandbox escape. Binance warned that "seed phrases, private keys and login credentials" could be at risk across the entire ecosystem.

## What you need before starting

- The iPhone in question, with access to Settings and the App Store.
- A list of installed apps, noting anything installed outside the App Store.
- A second, clean device (a phone or computer you trust, with no sideloaded software) for creating a new wallet if needed.
- Access to your exchange or wallet accounts so you can reset sessions.
- For businesses: access to your mobile device management (MDM) console, the tool that inventories and controls staff phones.

No spending is required. Everything below uses built-in settings.

## Step-by-step process

### Step 1: Identify which iOS version is running (2 minutes)

Open Settings, General, About, and read the iOS version. The reported vulnerable builds are 26.7.1, 27.0.1 and 27.2. Apple issued iOS 27.2.1 on Monday, but the release did not mention the sandbox escape, so it is not confirmed as a fix. Do not treat it as a reason to relax the later steps.

### Step 2: Audit for sideloaded apps (10 minutes)

The public proof-of-concept, a file manager called WQ Files, is installed through sideloading tools such as AltStore, SideStore or Sideloadly. Those tools automatically create the App Group container the exploit needs. Other signing tools, including Feather and ESign, can also be used, but the user needs a digital certificate and a provisioning profile that supports App Groups. Check for these tools and for any app you did not install from the App Store. Remove anything you do not recognise.

On company devices, pull the app inventory from MDM and flag anything signed outside the App Store.

### Step 3: Do not assume the App Store is a complete shield (5 minutes)

Most remediation talk has focused on cleaning up apps from outside the official store. Security community discussion cited in the source says authorised packages from trusted sources can also be hit by the Worse Query technique. Crypto security educator WiiMee points to fake wallet apps and to exploits such as DarkSword, which runs from Safari. So review any wallet app you have installed: is it the genuine publisher's app, and is it one you actually use? Delete the rest.

### Step 4: Decide whether to treat the device as compromised (5 minutes)

If you suspect a breach, treat the device as compromised. Binance's guidance is direct: if you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions.

### Step 5: Move funds and reset sessions

On the clean second device, create a new wallet and write down its recovery phrase offline. Send funds across from the old wallet. Then, in each exchange or wallet service, sign out all sessions, change passwords, and review any API keys or approved devices. Only then consider the old wallet retired.

## Common mistakes to avoid

- **Updating and stopping.** iOS 27.2.1 arrived without any mention of this flaw, so an update alone is not proof of safety.
- **Creating the new wallet on the suspect phone.** The point of Binance's advice is a clean device. A new wallet generated on a compromised handset inherits the risk.
- **Ignoring wildcard profile myths.** The source notes wildcard provisioning profiles cannot be used for this exploit because they lack App Group support. That narrows the paths, but a developer account or a compatible profile still works, so do not rely on it as a defence.

## Tips that make a difference

- Keep high-value crypto off any phone that has ever run sideloaded software. A device used purely for banking and messaging is a smaller target.
- The exploit gains the most on iOS 27, where, according to Kolbicz, the app reaches apps, backups, restores, clearing app data and the file browser without the limits seen on iOS 26. If you manage devices, prioritise iOS 27 handsets for inspection.

## UK position

## Key takeaways

- A public proof-of-concept exists and needs no jailbreak or kernel exploit.
- Apple's 27.2.1 release notes did not mention the flaw.
- The safe recovery path is a new wallet on a clean device plus session resets.
- Sideloaded apps are the easiest vector, but not the only one.

## Next steps

Watch for an Apple advisory that explicitly names the sandbox escape, and re-check once it appears. Businesses should add sideloading detection to their MDM policy and decide whether crypto-handling staff may use personal iPhones. Individuals should consider [passkeys or hardware security keys](/article/passkeys-vs-security-keys-yubikey/) for exchange accounts.

In short, you now know which iOS builds are affected, how to find sideloaded and untrusted apps, and how to move funds and reset sessions safely if a wallet may have been exposed.

## Sources

- [GovInfoSecurity](https://www.govinfosecurity.com/ios-sandbox-escape-puts-crypto-wallet-data-at-risk-a-33350)
- [NCSC, Device security guidance](https://www.ncsc.gov.uk/collection/device-security-guidance)
- [ICO, Personal data breaches](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/)
- [bankinfosecurity.com](https://www.bankinfosecurity.com/ios-sandbox-escape-puts-crypto-wallet-data-at-risk-a-33350)
