Skip to main content
AVOID.NET
← FomoPeekreviewed 2026-10-27 · 6 claims checked

Fact-check findings

What an automated fact-checker found when it re-read FomoPeek against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed 2unverifiable 1confirmed 32 corrections pending · 0 applied

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in section: Affected Versions and Timeline of Removal
    “According to search-aggregated reporting, Apple subsequently removed the application from the App Store, though Apple did not respond to Cointelegraph's request for comment before that outlet's publication.”
    reviewerApple removed FomoPeek from the App Store (section prose)No fetched source reports an Apple takedown. Page relies on unnamed 'search-aggregated reporting'.
    Proposed correction (not yet applied)
    Apple did not respond to Cointelegraph's request for comment before that outlet's publication, and the cited sources do not report whether the application was removed from the App Store.
  2. #2[disputed][awaiting moderator]in the timeline
    “Apple removed FomoPeek from the App Store following emergency threat disclosure. Apple had not responded to press requests for comment as of Cointelegraph's publication.”
    reviewerApple removed FomoPeek on 2026-09-22Both the event and its date (2026-09-22) are unsupported by the cited source. Consider removing the entry.
    Proposed correction (not yet applied)
    Apple had not responded to press requests for comment as of Cointelegraph's publication; no source reports the app's removal from the App Store.

unverifiable

1 claim

No source the reviewer could reach confirms or contradicts the claim.

  1. #5[unverifiable][awaiting moderator]in section: Malicious Payload: iOS Kernel Exploit Framework
    “covering iOS 12.0 through 18.7.2 and iOS 26.0 through 26.1”
    reviewerFramework covers 19 apps, iOS 12.0-18.7.2 and 26.0-26.1, eight methodsPrimary SlowMist source blocked. The technical specifics were not independently checked.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #3[confirmed][no action needed]in section: Financial Impact and On-Chain Attribution
    “approximately $401,028 USDT routed through three intermediary addresses to FixedFloat, $20,000 USDT sent to a KuCoin hot wallet, $111,458 USDT directed to an escrow platform address, and $10,000 USDT sent to the CCE mixing service”
    reviewerFund flow breakdown and attacker addressMatches CryptoSlate. Cointelegraph itself gives no per-service amounts, so attribution to it is loose.
  2. #4[confirmed][no action needed]in section: Affected Versions and Timeline of Removal
    “Version 1.1 (build 105), released September 9, 2026, introduced both malicious modules.”
    reviewerVersion dates and builds (1.1 build 105 Sept 9; 1.2 build 110 Sept 12; 1.3 build 111 Sept 17)Consistent across crypto.news and Cointelegraph.
  3. #6[confirmed][no action needed]in section: Industry Response and User Advisories
    “Binance further recommended that self-custody wallet holders create entirely new wallets on a separate, clean device that had never had FomoPeek installed, and transfer all assets to newly generated addresses.”
    reviewerBinance advisory recommendations and dateMatches.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.