Fact-check findings
What an automated fact-checker found when it re-read NEAR Intents Omni Exploit October 2026 ($3.8M) against the sources the page cites. Only the most recent review is shown.
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.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Incident Overview
“At approximately 15:43 UTC on October 1, 2026”
reviewerExploit began at about 15:43 UTC on Oct 1The specific time did not appear in the cited sources I read. The postmortem also says withdrawals ran Sept 29 to Oct 1, so Oct 1 is the pause date, not necessarily the start of the theft. - #12[unverifiable][awaiting moderator]in section: Fund Recovery and Resolution
“with the funds returned, the protocol indicated affected users' internal ledger balances would reflect pre-exploit amounts following accounting adjustments”
reviewerInternal ledger balances would reflect pre-exploit amounts after accounting adjustmentsNeither fetched source states this. The postmortem summary says all affected users were made whole.
stale
3 claimsThe claim was accurate when written but events since have overtaken it.
- #1[stale][awaiting moderator]in the summary
“a bug in the interaction between its Omni deposit/withdrawal infrastructure and its NEAR smart contract”
reviewerThe exploit was caused by a bug in the interaction between Omni infrastructure and the NEAR Intents contractEarly reporting matched the page, but the later postmortem, as reported by a secondary outlet, locates the flaw in the NEAR Intents contract and not in Omni.Proposed correction (not yet applied)a deposit-notification bug in the NEAR Intents contract, according to the project's October 16 postmortem - #2[stale][awaiting moderator]in section: Technical Vulnerability
“The exploit stemmed from a flaw in the integration between the Omni deposit and withdrawal layer and the upper-level NEAR Intents smart contract.”
reviewerSection 1 root cause: flaw in integration between Omni layer and the NEAR Intents contractSame underlying superseded root cause as the summary.Proposed correction (not yet applied)The exploit stemmed from a deposit-notification flaw in the NEAR Intents contract, according to the project's October 16 postmortem. - #3[stale][awaiting moderator]in section: Incident Overview
“a bug in the interaction between the Omni deposit and withdrawal infrastructure and the NEAR Intents smart contract”
reviewerSection 0 attributes the loss to an Omni/contract interaction bugSame defect as above.Proposed correction (not yet applied)a deposit-notification bug in the NEAR Intents smart contract, according to the project's October 16 postmortem
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #6[partially supported][awaiting moderator]in section: Incident Overview
“remained suspended for approximately 12 additional hours while Omni infrastructure repairs were completed”
reviewerDeposits and withdrawals on 11 networks stayed suspended about 12 more hoursThe 12-hour figure was an initial estimate. Later reporting says some routes reopened gradually over days. - #7[partially supported][awaiting moderator]in section: Fund Movement and On-Chain Tracing
“the stolen USDT was immediately transferred to the KuCoin exchange and subsequently bridged into Bitcoin”
reviewerZachXBT traced funds to KuCoin and bridged to BitcoinCore claim is supported. 'Immediately' is an embellishment. The attacker later returned the full amount, which sits uneasily with an unqualified account of the laundering path. - #9[partially supported][awaiting moderator]in the timeline
“2026-09-29”
reviewerBitget breach dated 2026-09-29Sources give no exact breach date. The 09-29 date matches the swap-block date (two days before Oct 1), not the breach, which was reported as about a week earlier.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #5[confirmed][no action needed]in section: Incident Overview
“which had processed over $30 billion in cumulative swap volume across 35 blockchains”
reviewerPlatform processed over $30 billion across 35 blockchainsSupported by Decrypt. The 'described by Polosukhin as the first major exploit' attribution was not found in the sources I read. - #8[confirmed][no action needed]in section: Preceding Bitget Incident Context
“NEAR Intents froze approximately $503,000 in funds connected to that incident and allowed approximately $166,000 through.”
reviewerNEAR Intents froze about $503,000 and let $166,000 through from the Bitget hacker's $50M attemptMatches Protos. Decrypt confirms the $50M attempt two days before the exploit. - #10[confirmed][no action needed]in section: Attacker Identification and Ultimatum
“'We have identified you, sir.'”
reviewerShevchenko announced exploiter identified on Oct 2 with a 48-hour ultimatum and three walletsQuotes and structure confirmed. Outlets disagree by a day on the ultimatum date. Law enforcement report is confirmed by Decrypt's recovery article, not by Cointelegraph. - #11[confirmed][no action needed]in the timeline
“NEAR Intents confirmed full recovery of the $3.8 million in stolen funds; declared the incident resolved and halted further investigation.”
reviewerFull recovery confirmed and investigation halted on Oct 2Confirmed. A search summary gave Oct 4 as the investigation close date, but the two articles I fetched both date it Oct 2.