NEAR Intents Loses $3.8 Million in Cross-Chain Exploit
A bug between the Omni deposit system and NEAR Intents smart contract led to a $3.8M loss; the project paused services and promised full repayment.
Cross-chain trading platform NEAR Intents lost about $3.8 million to an exploit on Thursday and paused services, disabling deposits and withdrawals on several blockchains, CoinDesk reports.
Timeline of the exploit
- 8:53 a.m. ET, October 1, 2026: the NEAR Intents team posts on X that it detected a security incident and halted the protocol, attributing the loss to "a bug in the Omni deposit and withdrawal infrastructure interaction with NEAR Intents smart contract" and giving a preliminary loss estimate of about $3.8 million 3.
- Within the following hour: the team says the contract-side flaw has been patched and that NEAR Intents and near.com are expected to resume operating 1.
- For roughly 12 more hours: deposits and withdrawals remain unavailable on 11 blockchain networks, including BNB Chain, Polygon, TON, Optimism and Avalanche, while the team finishes repairing the Omni infrastructure 3.
- Over roughly six hours: blockchain data shows about 3.87 million USDT (BSC-USD) leaving a NEAR Intents-labelled wallet on BNB Smart Chain in seven transfers 4.
What went wrong
The project blamed a bug in how its Omni deposit and withdrawal system interacted with the NEAR Intents smart contract. The flaw has been patched, and the team says affected users will be reimbursed in full. One investigator, the pseudonymous on-chain sleuth ZachXBT, said stolen funds were sent to KuCoin and converted to bitcoin — a common laundering pattern, since bitcoin's liquidity makes it easy to move value off-chain quickly 1.
Tracing data compiled by ZachXBT and blockchain analytics firm TRM showed the stolen funds split into two paths after leaving the theft address: one path involved a cluster of BNB transfers of roughly 100 BNB per transaction into deposit addresses that terminated at KuCoin, and another bridged into bitcoin, moving roughly 7.03 BTC onward between wallet addresses 4.
The pause of deposits and withdrawals across several chains suggests the team was unsure how far the flawed logic reached. That is a familiar pattern in cross-chain incidents: because one contract talks to many networks, a single bug can expose funds on all of them at once, so operators freeze everything until they can prove each connection is safe.
How NEAR Intents works
NEAR Intents lets users say what swap they want — for example, turning tokens on one chain into tokens on another — while independent "solvers" compete to complete it across chains. CoinDesk describes the system as designed "to make cross-chain trading simpler," so that instead of choosing a bridge, exchange or route themselves, users specify the swap they want and solvers compete to complete it behind the scenes 2. The platform says it has handled more than $30 billion in volume across 35 blockchains, making it one of the larger pieces of cross-chain infrastructure in crypto.
That design is powerful but concentrates risk. Users' funds pass through shared contracts and solver infrastructure, so a flaw in the plumbing can affect people who never interacted with the buggy component directly.
Market impact
The NEAR token fell 8.6% to $4.92 within hours, just two days after its first US spot ETF launched, BeInCrypto reported. The underlying NEAR blockchain itself was not the target — the exploit sat in the application layer built on top of it — but traders rarely make that distinction in the first hours of a hack.
The timing is awkward for the project. A spot ETF brings mainstream scrutiny, and a multimillion-dollar exploit days after launch hands skeptics an easy headline about crypto's security record. CoinDesk's report was explicitly framed around "crypto's rough year of hacks," underscoring that this incident landed amid a string of other exploits across the industry in 2026.
NEAR Intents' prior security posture
Notably, Unchained reported that the exploit came "days after NEAR Intents blocked Bitget hack funds," indicating the platform had recently been used as a tool to help freeze or flag funds tied to a separate, unrelated hack targeting the Bitget exchange 3. That detail suggests the protocol was already positioned as infrastructure that other platforms and investigators rely on for tracing illicit crypto flows, which makes a security flaw in its own systems particularly notable.
What the team has said
NEAR Intents said in its public post: "The preliminary report indicates the total loss of approximately $3.8M. These funds will be compensated in full" 3. CoinDesk also reported that the project said it had reported the incident to law enforcement and enlisted security firms to trace the stolen funds 2.
Why cross-chain systems keep getting hit
Bridges and cross-chain services connect systems with different security rules. Every connection point is a place where one side can be tricked into trusting a message it should not. They have been behind many of the largest DeFi losses in recent years, from the Ronin and Wormhole bridge hacks to this year's string of smaller exploits.
The core problem is complexity: a cross-chain protocol must correctly verify events that happened on another network, and each supported chain adds new edge cases. Auditors struggle to model every interaction, and attackers only need to find one.
What happens next
The team's promise of full reimbursement will now be watched closely. In past incidents, repayment pledges have ranged from prompt and complete to slow and partial, and the difference usually comes down to the size of the project's treasury. Users should expect a formal post-mortem and a claims process; anything less would be a red flag. As of the team's public statements, a fuller write-up of the incident was promised "in the coming days" 4.
What users should do
- Withdraw idle funds from cross-chain services instead of leaving balances there.
- Follow only the project's official channels for repayment details — fake "claim" sites usually appear within hours.
- Review and revoke old token approvals with a tool such as Revoke.cash.
- Treat any unsolicited "NEAR Intents refund" message as a scam until proven otherwise.
What readers should do
- Check official channels only — follow NEAR Intents' verified X account and near.com for the real reimbursement process; scam "claim" sites often appear within hours of a hack being publicised.
- Avoid rushing funds back in until the team publishes its promised full post-mortem explaining exactly what was fixed.
- Revoke old approvals to NEAR Intents or Omni-related contracts using a tool such as Revoke.cash if you interacted with the protocol before the patch.
- Track the reimbursement timeline — a full and prompt payout is the clearest signal the project is handling the incident responsibly; a slow or partial one is a warning sign for future use.
- Treat NEAR token price swings around the incident with caution — the drop was linked to the exploit and its ETF timing, not necessarily to a flaw in the underlying NEAR blockchain itself.
Sources & Verification
Additional reporting
- CoinDeskcoindesk.com
- BeInCryptobeincrypto.com
- The Blocktheblock.co
- Unchainedunchainedcrypto.com
- Crypto Timescryptotimes.io



