NEAR Intents stopped service on 1 October after irregular outflows from a BNB Smart Chain hot wallet.

The project said the preliminary loss is about $3.8 million, caused by a bug in the Omni deposit and withdrawal infrastructure and how it interacted with the NEAR Intents smart contract. It said users will be compensated in full, the contract-side flaw is patched, and the incident has been reported to law enforcement. A fuller write-up is promised in the coming days.

That account is in a post from @near_intents at 12:53 UTC. It was still the account’s only statement on the incident as of 18:45 IST. Alex Shevchenko, who speaks for the product, and @NEARProtocol had not posted on it. An earlier community alert, matched by a ZachXBT and TRM flow chart, put the same drain at more than $3.8 million and said the hot wallet had stopped processing.

The one-hour restart the post promised for NEAR Intents and near.com had not been confirmed in a follow-up.

What left the NEAR Intents BSC hot wallet

The theft address in the alert is 0x89fd1f5d9f185067a92493e43aa259ea4ab3ad37.

The flowchart shows 3,865,001 BSC-USD in seven transfers, moving from a NEAR Intents-labeled wallet into that address on 1 October. From there the funds split. One path is a cluster of BNB transfers, about 100 BNB a leg, into deposit addresses that terminate at KuCoin. Another path bridges into Bitcoin: about 7.03 BTC to bc1qwk…v7p0, then about 7.03 BTC onward to bc1qey…tsn8.

Those are tracer figures, not the project’s final accounting. NEAR Intents has not published a token-by-token table. The $3.8 million line is what the team called preliminary.

The hot wallet at 0x233c, named in the alert, had stopped sending. That is an operational stop, not a proof the key is gone. The project’s own wording points at a contract-interaction bug in the Omni deposit and withdrawal path, not at a stolen user seed.

Why deposits stay down on 11 chains

The Shield status page showed open incidents on Plasma, ADI, Scroll, Stellar, Optimism, Avalanche, BNB Smart Chain, Polygon, TON, Monad, and X Layer, plus a hot-bridge flag. Several of those were opened about three hours before the intents-level flags.

NEAR Intents said swaps on NEAR Intents and near.com should resume within about an hour of the post. Deposits and withdrawals stay down for about 12 more hours on BSC, Polygon, TON, Optimism, Avalanche, Stellar, Monad, LayerX, Adi, Scroll and Plasma while the Omni fix is finished.

Users holding assets from those chains inside NEAR Intents, including in the HOT wallet or on near.com, were told they can swap into other assets once the service is back, without waiting on the deposit rails.

Law enforcement has been notified. The team said it is working with security and analytics firms to trace funds. No recovery total has been published. KuCoin has not confirmed a freeze on the deposit addresses in the chart. The compensation promise has no wallet, no token list and no paid amount attached to it.

How this differs from last week’s Bitget block

Three days ago NEAR Intents was on the other side of a theft. Its SHIELD checks refused most of a $50 million attempted flow from the Bitget hack, froze $503,000 mid-swap, and let $166,000 through.

This incident is the project’s own BSC hot-wallet path, not a third-party laundering attempt. The team is saying the loss sits with the infrastructure bug and will be repaid from its side. That repayment claim is a promise. It is not a completed transfer.

No user-by-user shortfall has been posted. Anyone with a stuck deposit on the 11 paused chains is waiting on the Omni fix, not on the one-hour swap restart.

Also Read: NEAR Intents Blocked $50M in Bitget Hack Funds, but Only $503K Was Frozen