Cybersecurity

Binance's iOS Alert: Understanding the Risks of the worse_query Flaw

A public exploit lets one iPhone app read another app's files, but no thefts have been reported and Apple's fix status is unclear.

12 min read
Isometric cutaway of a phone-shaped building with separate sealed rooms, one door slightly open with a warm line of light.
AI-generated illustration

Binance warned on November 10 about an iOS flaw called worse_query that lets a malicious app read other apps' local files. Reports describe file access, not confirmed theft, and the route typically runs through sideloaded apps. Whether Apple has patched it remains disputed.

An iPhone owner who holds crypto does not appear to face an automatic threat from the flaw Binance flagged on November 10, 2026, but the flaw is real and a working public tool exists. According to reports relaying the researcher's code, it lets one app read files that belong to other apps. That matters mainly if an untrusted app is installed on the phone and a wallet leaves its secrets in readable files.

No theft tied to the flaw has been reported by Binance or by the researcher, and BleepingComputer, as relayed by other outlets, says there is no evidence of attackers using it against crypto holders. Whether Apple has fixed the problem is disputed. This article separates what the reporting establishes from what remains inference, and it lays out the protective steps that were actually sourced during this episode.

What Binance warned about, and where the flaw came from

Binance posted its warning on X on Tuesday, November 10. According to news reports quoting the post, the exchange said a vulnerability named worse_query, affecting iOS 26.7.1, 27.0.1 and 27.2, allows malicious apps to read local files from other apps. Binance added that this is an iOS-level problem and not specific to Binance.

Binance did not discover the bug. Reporting traces it to a researcher who posts as forcequitOS and published worse_query on GitHub on November 8. The researcher described it as "a zero-day sandbox escape for iOS 26 and 27, again," and presents it as the successor to an earlier technique called bad_query, which BankInfoSecurity places in August 2026. In effect, the exchange relayed a public proof of concept to its customers.

The warning also carried advice. Binance told users to delete apps installed from untrusted sources, such as sideloaded or manually signed IPA files, and to update iOS and every app to the latest official versions. It said anyone who suspects a breach should move funds to a new wallet created on a clean device and reset all active login sessions.

What the technique can reach

On iOS, each app is supposed to live inside its own container that other apps cannot read. According to CyberInsider, which relayed the researcher's repository, worse_query can reach app data containers, extension data, internal daemon containers and shared App Group storage, with additional system paths accessible on iOS 27. That description has not been checked against the repository itself.

A second development raised the stakes. Developer Christoph Kolbicz built WQ Files, a file browser and app data manager that reimplements the technique without a kernel exploit. As reported by tbreak, it can browse, export, edit and delete other apps' data without a jailbreak, and BleepingComputer confirmed it works on all three versions Binance named. The researcher, for his part, called the standalone code a developer proof of concept that "isn't useful by itself."

Which iPhones are affected

Binance named three builds, but the reporting suggests the real range is wider. The researcher's README, as reported, says the exploit works on iOS 26.0 through 26.7.2 and on iOS 27.2. Several outlets, including Fdaytalk and Cryptonomist, noted that Binance's three versions match the ones listed as tested in the WQ Files release notes. That match points to a likely reason for the narrower list, though it is inference and Binance has not explained its choice.

Version claims about worse_query, as reported in November 2026
Source Versions stated Notes
Binance X post, Nov. 10 26.7.1, 27.0.1, 27.2 Matches the versions the WQ Files release notes list as tested
forcequitOS GitHub README (as reported) 26.0 through 26.7.2, plus 27.2 Wider range; comes from the exploit's author
BleepingComputer test (as reported) WQ Files works on 26.7.1, 27.0.1, 27.2 Tested only the versions Binance named
Erosion developers 27.2.1 "pretty sure" works Unverified and hedged
Predecessor bad_query (per KuCoin News) 26.0–26.6.1, 27.0 beta 4 Earlier technique
Apple releases, Nov. 9 27.2.1, 26.7.3, 18.7.12 Whether they fix worse_query is unconfirmed

Gaps remain inside that range. Binance does not explicitly address iOS 27.0 without the .1, 27.1 or 26.7.2, and the researcher's range appears to cover 26.7.2 but could not be confirmed for 27.0.x or 27.1 from the sources. None of the reports reviewed says iOS 18 is affected. The practical reading is that the working set is the researcher's range plus Binance's 27.0.1, held with moderate confidence.

File access is not the same as stolen crypto

The headline versions of this story, "exposes seed phrases," compress several steps into one. As described, the flaw is not remote, and it does not take anything by itself. SlowMist, the blockchain security firm, said: "The bug does not steal assets by itself." It needs a malicious or untrusted app already running on the phone.

What the attack requires

According to BankInfoSecurity, the exploit requires an App Group container, a legitimate iOS feature that lets authorized apps share data. Kolbicz told the outlet that sideloading tools such as AltStore, SideStore or Sideloadly create that container automatically, which makes them the easiest route. This is a single-outlet account.

Sideloading means installing apps from outside the App Store, for example through signed IPA files. It is not how most iPhone owners get their apps, but no source reviewed quantifies how many US iPhone owners sideload. Whether an ordinary App Store app could use the technique is not addressed in any source found, so it cannot be said either way.

Where the seed phrase comes in

SlowMist says the real risk begins when a user installs an app from an untrusted source. If a wallet stores its seed phrase, keystore or WebView cache in plaintext on the device, a malicious app with file access could read it. By the same reading, wallets that do not write recovery phrases or keys to plain files are not exposed in the same way, and hardware wallets keep private keys off the phone entirely.

Expert commentary reported by eSecurityPlanet adds a caution. Access to an app's files does not necessarily let an attacker retrieve credentials protected by the iOS Keychain or other encryption. That is a caveat rather than a tested result, but it shows why the leap from "can read files" to "can empty a wallet" is not automatic.

No source reviewed shows the proof of concept pulling a seed phrase out of a named, real wallet app. Binance, the researcher and the developers building tools around the escape did not identify a specific wallet as exposed. The claim that the flaw exposes seed phrases is an inference from general file access combined with plaintext storage, and the 24/7 Wall St. suggestion that phrases saved in Notes, Photos or screenshots could be exposed is not supported by any description of the research. Whether the technique reaches Apple's own apps' data is not established.

Has Apple fixed it? The sources disagree

Apple released iOS 27.2.1 and iPadOS 27.2.1 on November 9, along with iOS 26.7.3 and iOS 18.7.12. According to outlets quoting the security notes, the notes for 27.2.1 and 26.7.3 do not mention worse_query or any sandbox escape. That silence settles little, because Apple's standing policy is not to disclose, discuss or confirm security issues until an investigation has occurred and patches or releases are available.

One entry is potentially related. Under App Intents, Apple says an app may be able to access sensitive user data, and that an authorization issue was addressed with improved state management. The entry is CVE-2026-113963, credited to László Várady. Whether it is the same bug is unconfirmed: the text refers to App Intents rather than App Group containers, and BleepingComputer says it is unclear. The credited reporter is also a different person from the worse_query researcher, which may hint at a different bug, though that is an inference.

The case that it is fixed

SlowMist's chief information security officer, 23pds, urged users to update to iOS 27.2.1, saying the update would block the worse_query sandbox escape. That comes from one person's post relayed by Decrypt, and no technical evidence accompanied it.

The case that it is not

The researcher said on November 10 that the flaw remained active in both iOS 27.2.1 and the first beta of iOS 27.3. Developers of another app built on the technique, Erosion, added 27.2.1 to their README with a note that they were "pretty sure" it works. Nobody lists iOS 26.7.3 as supported. The people making these claims have an interest in their tools working, and the researcher's statement covers 27.2.1 and 27.3 beta 1, not 26.7.3. 9to5Mac and AppleInsider reported on November 11 that it was an unpatched exploit.

BleepingComputer contacted Apple for clarification, according to Gulf News, and no Apple response turned up. The honest status is unresolved. An Apple entry crediting forcequitOS, or an independent test on a clean 27.2.1 or 26.7.3 device, would settle it. Updating is still reasonable, since those releases fix other flaws, but nobody should be told the problem is certainly gone or certainly present.

Timeline of the worse_query episode, 2026
Date Event
August bad_query, the predecessor technique, is released
Nov. 8 worse_query posted to GitHub; SlowMist flags the proof of concept
Nov. 9 Apple ships iOS 27.2.1, 26.7.3 and 18.7.12
Nov. 10 Binance posts its X warning; SlowMist issues an alert; researcher says it still works on 27.2.1 and 27.3 beta 1
Nov. 11 9to5Mac and AppleInsider report it as unpatched

How serious is it, and how do competing readings differ?

Binance's wording was broad, describing risk across the whole crypto ecosystem. SlowMist and other commentators narrowed it: the attack needs a sideloaded or malicious app, and it only helps if secrets sit in readable files. An exchange's warning to its customers is also a sector-wide caution rather than a technical advisory, and it comes from a company with its own interest in keeping users alert.

Some counterevidence points toward lower real-world risk. There are no reports of loss. Apple's language on the nine vulnerabilities in the 27.2.1 notes does not say any were used in real attacks, though that refers to those nine CVEs, not worse_query. The reporting is also thin on independence: much of it traces back to Binance's post, BleepingComputer, Decrypt and SlowMist, so repetition across outlets is not the same as independent confirmation. No independent security-lab analysis, Apple statement or CVE assignment was found.

The warning also followed a separate SlowMist alert about DarkSword, a different iOS exploit framework aimed at crypto users. The two involve different reported threats, and one should not be read as evidence that the other is part of the same campaigns.

Protecting a seed phrase during this episode

The steps below are the ones Binance and SlowMist put forward in response to this flaw. They are researched context rather than personal advice, and they are limited to what the sources support.

  • Update iOS and every app to the latest official versions, as both Binance and SlowMist advise. The update may or may not close this specific hole, but the same releases patch other reported flaws.
  • Delete sideloaded or manually signed apps, and avoid installing apps from unknown sources. The reported attack route depends on an untrusted app being present.
  • Do not keep recovery phrases or keys in plaintext on the phone. SlowMist raised this point for wallet developers and users alike.
  • Consider where private keys live. By SlowMist's reading, hardware wallets keep private keys off the phone entirely, so file access on the phone does not reach them.

If exposure is suspected

Binance's advice for a suspected breach is to create a new wallet on a clean device, move the funds and reset all active login sessions. The logic, echoed in commentary from CyberInsider and Crypto Economy, is that a copied secret stays valid. Deleting the offending app or updating iOS afterward does not undo a copy, so only a new phrase restores safety.

A weaker source, 24/7 Wall St., says an offline seed phrase stays safe on every iOS version. The reasoning is sensible, since a phrase that never touches the phone cannot be read from it, but the claim needs a better citation than this brief provides. Broader seed phrase storage practices, such as backup methods and passphrase options, were not covered by any source retrieved and are left out here.

What this means, and what to watch

The episode is a reminder that phone security and wallet security are separate layers. A flaw in the operating system's app isolation becomes dangerous to crypto holders only when two other conditions line up: an untrusted app gets onto the device, and a wallet stores something valuable where that app can read it. Removing either condition changes the outcome, and the second is largely in the hands of wallet developers.

The open questions are concrete. An Apple statement or a CVE crediting forcequitOS would resolve the patch dispute. A published test against a real wallet would show whether the seed phrase worry is practical or theoretical. Until then, the evidence supports a measured stance: a real, public flaw with no reported victims, a narrow route of attack, and an unsettled fix.

Frequently asked questions

Is my iPhone affected by the worse_query flaw?

Binance named iOS 26.7.1, 27.0.1 and 27.2. The researcher's README, as reported, covers iOS 26.0 through 26.7.2 and 27.2, a wider range. Exploitation also requires an untrusted app, typically a sideloaded one, to be installed on the phone.

Has anyone lost crypto because of this flaw?

No thefts have been reported by Binance or the researcher, and BleepingComputer reports no evidence of attacks on crypto holders. That is an absence of reports, which is not proof that nothing has happened.

Did Apple patch worse_query in iOS 27.2.1?

That is unresolved. Apple's notes for 27.2.1 and 26.7.3 do not mention it, SlowMist's security chief said 27.2.1 blocks it, and the researcher said it still works on 27.2.1 and the first 27.3 beta. No Apple response has been found.

Can the flaw read a seed phrase stored in the iPhone Notes app?

No source establishes that. The proof of concept is described as reaching app containers and App Group storage, and whether it reaches Apple's own apps' data has not been shown.

What should someone do if a seed phrase may have been exposed?

Binance advises creating a new wallet on a clean device, moving the funds there and resetting all active login sessions. Updating iOS or deleting an app does not make a copied phrase safe again.

Sources (17)

  1. Binance Warns IOS Flaw Could Expose Wallet Seed Phrases , Bitcoin Magazine
  2. Binance warns iOS sandbox escape could expose crypto wallet secrets , CyberInsider (2026-11-10)
  3. Binance Warns of Apple iOS Flaw That Could Expose iPhone Users' Private Keys , Decrypt
  4. Binance warns iPhone crypto holders of security flaw , 9to5Mac (2026-11-11)
  5. Unpatched exploit allows malicious iOS apps to steal data , AppleInsider (2026-11-11)
  6. iOS flaw worse_query lets apps read other apps' files , tbreak
  7. iOS Sandbox Escape Puts Crypto Wallet Data at Risk , BankInfoSecurity
  8. New iOS Exploit Could Expose Data From Other Apps , eSecurityPlanet
  9. SlowMist Warns of iOS Sandbox Escape Risk Exposing Wallet Data , KuCoin News
  10. Binance Warns iOS Flaw Puts Seed Phrases at Risk From Malicious Apps , CoinMarketCap Academy
  11. IOS sandbox escape vulnerability risks crypto wallet security , Cryptonomist (2026-11-10)
  12. Binance Warns of iOS Sandbox Escape Exposing Crypto Wallet Keys , Fdaytalk
  13. Binance Flags iOS Flaw That Could Expose Crypto Wallet Keys Across Ecosystem , Crypto Economy
  14. Binance warns iPhone flaw could expose crypto wallet secrets , Gulf News
  15. Apple's iOS 27.2.1 Update Leaves Crypto Wallet Security Flaw Unpatched , Bitbase
  16. Binance Warns an iPhone Flaw Could Expose Crypto Seed Phrases. Which iOS Versions Are at Risk? , 24/7 Wall St. (2026-11-10)
  17. Apple Fixes 9 Security Vulnerabilities in iOS 27.2.1, Including Bluetooth Pairing and iMessage Flaws , Cyber Security News (2026-11-10)

Share this article

Back to list