Skip to main content
AVOID.NET
← NEAR Intents Omni Exploit (October 2026)reviewed 2026-10-28 · 10 claims checked

Fact-check findings

What an automated fact-checker found when it re-read NEAR Intents Omni Exploit (October 2026) 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.

stale 2partially supported 3confirmed 52 corrections pending · 0 applied

stale

2 claims

The claim was accurate when written but events since have overtaken it.

  1. #2[stale][awaiting moderator]in section: Technical Cause
    “According to NEAR Intents' own account, the exploit arose from a contract-side flaw in how the Omni custody/bridging layer communicated with the primary NEAR Intents smart contract, rather than from a compromise of a private key or exchange account.”
    reviewerCause was a flaw in Omni infrastructure interaction with core contract, not a key compromise (superseded by post-mortem)Early framing is superseded. The page also says no post-mortem exists at time of writing, which is no longer true. I read only secondary coverage of the post-mortem, not the original.
    Proposed correction (not yet applied)
    According to NEAR Intents' initial statement, the exploit arose from a bug in the interaction between the Omni deposit and withdrawal infrastructure and the NEAR Intents smart contract. A post-mortem published October 16, 2026 instead placed the flaw in the NEAR Intents contract's deposit notification function: an attacker-built contract made the notification fail, so the token contract refunded the deposit while NEAR Intents kept the ledger credit, creating about $3.8 million in unbacked balances across 23 failed deposits that were then withdrawn through Omni.
  2. #3[stale][awaiting moderator]in section: Technical Cause
    “though this detail has not been independently confirmed by a post-mortem report at the time of writing”
    reviewerNo post-mortem has been publishedPost-mortem now exists. I did not confirm whether it mentions the BNB hot wallet, so the proposed wording is a weaker fit; the judge may prefer simply removing the clause.
    Proposed correction (not yet applied)
    though this detail was not addressed in the post-mortem published on October 16, 2026

partially supported

3 claims

The cited evidence supports part of the claim but not all of it.

  1. #4[partially supported][awaiting moderator]in section: Technical Cause
    “with full deposit and withdrawal functionality across affected networks restored after approximately 12 hours.”
    reviewerPatched and services restored after about 12 hoursCited source gives a forecast. Post-mortem coverage says the contract reopened Oct 1 or Oct 2, with a second bug patched Oct 7. Restoration at 12 hours is not confirmed.
  2. #7[partially supported][awaiting moderator]in section: Response, Reimbursement Pledge, and Market Impact
    “The incident has been reported to law enforcement, and we are working with security and blockchain analytics partners to trace the funds and pursue recovery.”
    reviewerFull reimbursement pledge and law-enforcement quoteOpening of the quote matches; the tail could not be verified from the fetch.
  3. #8[partially supported][awaiting moderator]in section: Response, Reimbursement Pledge, and Market Impact
    “Following the news, the NEAR token fell sharply, with reporting citing declines of roughly 7.5 to 8.9 percent and a low near $4.76-$4.86, and shares of a recently launched NEAR-linked exchange-traded fund also dropped more than 7 percent.”
    reviewerNEAR token fell roughly 7.5-8.9%, low near $4.76-$4.86; NEAR ETF fell more than 7%ETF and the 8.93% figure confirmed; the range is only partly checked.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: The Exploit
    “On October 1, 2026, NEAR Intents, a cross-chain intent-based swap protocol built on NEAR Protocol, halted service after an attacker drained approximately $3.8 million in user funds.”
    reviewerExploit of about $3.8M on October 1, 2026, with deposits and withdrawals paused across 11 networksAmount, date and pause confirmed. Note the post-mortem says withdrawals ran Sep 29 to Oct 1, so the drain was not a single-day event.
  2. #5[confirmed][no action needed]in section: Fund Flow and On-Chain Tracing
    “On-chain investigator ZachXBT reported that the stolen funds were sent to the KuCoin exchange and subsequently bridged into Bitcoin”
    reviewerZachXBT reported funds went to KuCoin and bridged to BitcoinAccurately reported as ZachXBT's claim.
  3. #6[confirmed][no action needed]in section: Fund Flow and On-Chain Tracing
    “As of publication of the cited reporting, the identity of the attacker had not been established.”
    reviewerAttacker identity had not been established (stale: funds reportedly returned)Correctly scoped to the cited reporting. The later return of funds is handled as an omission.
  4. #9[confirmed][no action needed]in section: Context: Preceding Bitget Hack Intervention
    “The exploit occurred roughly two days after NEAR Intents had reportedly blocked a $50 million swap attempt and frozen over $500,000 linked to the perpetrator of a separate, much larger theft of approximately $387.5-388 million from the exchange Bitget”
    reviewer$50M swap blocked and over $500,000 frozen, tied to Bitget attacker; Bitget theft about $387.5-388MCombined across both sources. The Bitget CEO's North Korea speculation is in Cointelegraph, but the IP-evidence basis was not checked.
  5. #10[confirmed][no action needed]in the timeline
    “deposits and withdrawals on 11 networks remain paused for roughly 12 additional hours.”
    reviewerTimeline: 12 additional hours pause after patch statementMatches the Decrypt statement as of Oct 1.
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.