TLDR
A bug in NEAR Intents cross-chain infrastructure allowed an attacker to drain about $3.8 million from user funds before services were halted.
- NEAR Intents Omni deposit-and-withdrawal system misbehaved with its main smart contract, letting roughly $3.8 million be stolen and forcing a pause across multiple networks.
- The stolen funds moved from a USDT pool on BNB Chain to KuCoin and then into Bitcoin, while NEAR Intents pledges full reimbursement and has patched the contract-side vulnerability.
- The incident highlights growing structural risks in cross-chain intent systems and comes amid a broader spike in large crypto hacks, making future audits and post-mortems important to watch.
Deep Dive
1. What Went Wrong Technically
Reports say NEAR Intents, a cross-chain trading protocol, suffered a security exploit on 1 Oct that caused about $3.8 million in losses after a bug in how its Omni deposit-and-withdrawal layer interacted with its smart contract.Coindesk and Cointelegraph both attribute the incident to this integration flaw.
The protocol halted services and temporarily disabled deposits and withdrawals on at least 11 networks, including BNB Smart Chain, Polygon, ethereum/">Optimism, Avalanche, TON, Stellar and Scroll, while fixing the infrastructure bug.TokenPost notes the vulnerability has been patched on the contract side, with Omni infrastructure repairs continuing.
The failure wasnt a classic single-chain contract exploit, but a bug at the junction where cross-chain infrastructure and custody logic meet, which is a particularly fragile part of many bridge-like systems.
2. How Funds Moved And Who Is Affected
Investigators say the stolen funds were held in a USDT pool on BNB Chain, then rapidly moved through a hot wallet to KuCoin and bridged into Bitcoin, complicating recovery.TokenPost and on-chain analyst ZachXBTs tracing cited in Bitcoin.coms report describe this path.
NEAR Intents has publicly pledged to compensate in full the roughly $3.8 million in affected user funds, though detailed reimbursement timelines and user-by-user breakdowns have not yet been published.Yahoo Finance notes that the team has reported the incident to law enforcement and engaged security firms to trace the funds.
Market-wise, the NEAR Protocol (NEAR) token dropped around 79% intraday after the announcement, and a recently launched NEAR ETF also fell, even though the flaw is in cross-chain infrastructure rather than the base NEAR blockchain itself.U.Today and The Blocks recap highlight the price reaction.
3. Broader Security Context And What To Watch
This exploit lands in a heavy year for crypto security incidents, following large breaches at Bitget and others.Coindesks coverage frames NEAR Intents within a wave of 2026 hacks.
Key next signals are:
- A detailed public post-mortem explaining the exact bug and mitigation steps.
- Concrete reimbursement mechanics (who is repaid, in what asset, on what schedule).
- Any changes to hot-wallet limits, cross-chain custody design, and third-party integrations.
For users of cross-chain protocols, this is a reminder to treat intents systems and bridge-like infrastructure as higher-risk than simple on-chain swaps, especially where funds sit in pooled custody across multiple networks.
Conclusion
A relatively small but high-impact bug at the junction of NEAR Intents cross-chain infrastructure and its smart contract allowed about $3.8 million in user funds to be drained and quickly moved across networks.
If the team delivers full reimbursement and transparent technical and security changes, the immediate damage can be contained, but the incident reinforces a broader lesson: cross-chain systems concentrate risk in complex plumbing where failures can propagate quickly across many chains.
CoinsKid.Com