NEAR Intents Exploit: What to Do With Cross-Chain Deposits and Withdrawals
NEAR Intents halted services after an exploit reportedly caused about $3.8M in losses and disrupted deposits and withdrawals across multiple networks.
Crypto Support & Research Desk
Direct answer: NEAR Intents halted services on October 1 after an exploit reportedly caused about $3.8 million in losses. Reporting said the flaw involved the interaction between Omni deposit/withdrawal infrastructure and the NEAR Intents smart contract. The contract issue was patched, but deposits and withdrawals across 11 networks were expected to remain disrupted longer. If you had a cross-chain transfer in flight, preserve every transaction hash and do not repeat the swap until you know where the original funds are.
What happened?
NEAR Intents enables cross-chain asset movement through intent-based infrastructure. According to reporting from The Block, the team halted services after identifying a contract flaw and said it would compensate losses. The affected workflow included deposit and withdrawal infrastructure, making this directly relevant to users whose transfers were mid-route.
How to check an in-flight transfer
- Identify the source chain and destination chain.
- Copy the source transaction hash from your wallet.
- Check whether the source transaction succeeded.
- Record any NEAR Intents order, deposit or route identifier shown by the interface.
- Check the destination wallet independently rather than relying only on the app interface.
- Save screenshots and timestamps for support.
Do not repeat the cross-chain swap yet
Cross-chain systems can pause between source confirmation and destination settlement. Repeating the transaction may create another transfer rather than repair the first. Wait until the protocol publishes restoration guidance or support confirms the status of your original route.
Networks and service disruption
Reporting said deposits and withdrawals on 11 blockchain networks, including BSC, Polygon and Optimism, faced extended disruption during the response. Treat each route independently because restoration timing can differ by network.
Security precautions
Revoke unnecessary token approvals if you interacted with unfamiliar contracts, but do not randomly revoke or sign transactions from links sent in social media replies. Use official protocol channels to identify contract addresses. Never enter a seed phrase into a recovery website.
Compensation and recovery claims
The team reportedly pledged full compensation. That does not mean users should trust unsolicited claim links. Wait for an official claims or reimbursement process and verify its domain through the protocol’s established channels.
Source
The Block report on the NEAR Intents incident.
FAQ
Was NEAR Intents exploited?
Yes, according to the team statements reported by The Block.
Are all transfers lost?
No. A service halt or delayed cross-chain settlement does not by itself mean an individual transfer is lost.
Should I send the transaction again?
Not until you have verified the state of the original route.
Informational only; not investment, trading, legal or tax advice. Security incidents evolve quickly, so verify current protocol guidance before signing transactions.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.