Google Analytics counts our visits, with cookies. No thanks turns it off and removes its cookies; in Europe, the UK, Switzerland and India, or wherever we cannot tell where you are, it stays off unless you accept. Cookie Notice

Advertise
PRICES

← Back to Originals

InvestIn.News OriginalAnalysis

Near Intents hit by $3.8m exploit as team promises full compensation

A Telegram alert flagged irregular outflows from Near Intents' BSC hot wallet on 1 October. The team says a bug in Omni's deposit and withdrawal infrastructure is to blame and that users will be repaid in full.

Why it matters: The exploit shows that even protocols with strong monitoring can lose funds through a partner's bug, and users are promised full repayment but have no timeline yet.

·Founder · Markets desk · 5 min read

Reviewed and fact-checked by Ishu Aggarwal

Share
Illustration: “Near Intents hit by $3.8m exploit”, with bitcoin, ai network, lock icons in InvestIn.News colours

In short

  • Near Intents lost more than $3.8m from its BSC hot wallet 0x233c, according to a 1 October Telegram alert.
  • The team says a bug in Omni's deposit and withdrawal infrastructure caused the exploit and that funds will be compensated in full.
  • Deposits and withdrawals on 11 chains, including BSC and Polygon, are down for about 12 hours while fixes are made.
  • NEAR fell 6.27% in 24 hours to 1 October, as the total crypto market dropped 4.24%.

What is Near Intents

Near Intents is a cross-chain protocol built on the NEAR blockchain. It lets users swap assets across different blockchains without using a traditional bridge. NEAR is a layer-1 network that positions itself as a fast, low-cost chain for consumer and AI applications. The protocol has handled roughly $30bn in volume, according to Bitwise, which cited that figure in a September report.

What happened

Near Intents, a cross-chain protocol built on the NEAR blockchain, lost more than $3.8m after its BSC hot wallet saw a series of irregular outflows, according to a community alert posted on Telegram on 1 October. The wallet, identified as 0x233c, has stopped processing transactions, and the project's status page shows an ongoing incident affecting several EVM chains. The funds were moved to KuCoin and bridged to Bitcoin, the alert said, citing blockchain investigator ZachXBT. The theft address on BSC is 0x09fd1f5d9f185067a92493e43aa259ea4ab3ad37.

Near Intents is a protocol that lets users swap assets across different blockchains without using a traditional bridge. It runs on NEAR, a layer-1 network that positions itself as a fast, low-cost chain for consumer and AI applications. The protocol has handled roughly $30bn in volume, according to Bitwise, which cited that figure in a September report.

How it happened

The team posted a preliminary report at 12:53 UTC (8:53 a.m. ET) on 1 October, about an hour after the community alert. It said services were stopped after a security incident and that the cause was a bug in how Omni's deposit and withdrawal infrastructure interacted with the Near Intents smart contract. The estimated loss is about $3.8m, and the team said those funds will be compensated in full. The contract-side vulnerability has been patched. The announcement did not include transaction hashes or a token-by-token breakdown of the loss.

Core services on Near Intents and near.com were expected to resume within about an hour of that post. Deposits and withdrawals on BSC, Polygon, TON, Optimism, Avalanche, Stellar, Monad, LayerX, Adi, Scroll and Plasma were to stay down for roughly another 12 hours while Omni infrastructure fixes are finished. Assets already inside Near Intents from those chains, for example in the HOT wallet or on near.com, were expected to be swappable into other assets once core services came back.

The team said it reported the incident to law enforcement and is working with security and blockchain analytics partners to trace the funds and pursue recovery. A detailed public report is promised in the following days.

Who is affected

For ordinary users, the immediate question is whether their own funds are safe. The team's statement suggests assets held inside the protocol were not drained and that swaps should work again once services restart. But the full-compensation promise covers the stolen $3.8m, not necessarily every user's balance, and it is not yet clear how or when payouts will be made. Anyone with funds on the affected chains should watch for the detailed report before assuming everything is back to normal.

Traders, meanwhile, will be watching the NEAR token, which fell 6.27% in the 24 hours to 13:53 UTC on 1 October, according to InvestIn.News market data. Bitcoin was at $83,757, down 0.94%, and the total crypto market value stood at $2.88tn, down 4.24%. The Fear & Greed Index read 74 of 100, in Greed territory. It is not clear whether the exploit contributed to the NEAR move or whether the token was caught in a broader market pullback. The outage interrupts a system that handled about $4.8bn in swap volume over the past 30 days, according to DefiLlama.

This is not the first time Near Intents has been in the news for security. On 28 September, Aurora co-founder Alex Shevchenko said attackers in the 24 September Bitget hack tried to move more than $50m in stolen funds through Near Intents. The protocol's SHIELD risk intelligence layer detected the flows, with about $166,000 passing through and roughly $503,000 frozen, according to Wu Blockchain. Bitget CEO Gracy Chen said the exchange lost about $388m in that hack, with much of the money moved cross-chain and gathered on Ethereum, according to Odaily.

The Bitget episode showed Near Intents' monitoring tools working as intended. This time, the loss came from a bug in a partner's infrastructure rather than a failure to spot suspicious flows. That distinction matters for how users judge the protocol's security posture.

There are no public reactions from users or the team beyond the preliminary report. The community alert came from a Telegram channel that credited ZachXBT, but neither Near Intents nor ZachXBT's own channel has posted further details. The team's report is the only confirmation so far, and the $3.8m figure and the full-compensation promise have not been verified by anyone else.

What happens next

The next concrete step is the detailed public report the team has promised in the coming days. Until then, the exact sequence of the exploit, the full list of affected users and the mechanics of compensation remain unclear. Deposits and withdrawals on the listed chains are expected to stay down for about 12 hours from the 12:53 UTC post while Omni fixes its infrastructure. For other incidents of this kind, see our hacks coverage.

Our view

Hacking has become a persistent feature of this industry, and the Near Intents exploit is the latest reminder that security is never a finished product. The protocol's own SHIELD system performed well during the Bitget hack in September, freezing roughly $503,000 of stolen funds. That success did not prevent a $3.8m loss this time, because the weakness lay in Omni's deposit and withdrawal infrastructure rather than in Near Intents' monitoring. The team deserves credit for a swift preliminary report and a promise of full compensation, but a promise is not a payment. Until the detailed report names the exact failure and sets out a timeline for repayment, users have little more than reassurance. The test will be whether the compensation arrives in full and on schedule.

Follow the latest updates as they happen on NewsFeeds.

Keshav Aggarwal

Sources

What to watch: Near Intents has promised a detailed public report in the coming days; deposits and withdrawals on affected chains are expected to stay down for about 12 hours.

Live updates on NewsFeeds:ETFsBy Keshav Aggarwal

Disclosure: Keshav Aggarwal holds small amounts of crypto as long-term investments. He does not trade any asset he writes about within 24 hours of a story, and is not paid by any company covered on this site, updated 6 October 2026. Our holdings and trading policy.

How this was produced: the writer drafted this piece with AI help, from the reporting and sources it names, then checked and edited it. Read our Editorial and AI policy. Spotted a mistake? See Corrections.

Not investment advice. Read the risk disclaimer.

← Back to Originals