NEAR Intents Halts Swaps After $3.8M Leaves a BSC Hot Wallet

NEAR Intents Halts Swaps After $3.8M Leaves a BSC Hot Wallet


$3.8 million drained from NEAR Intents BSC hot wallet due to a contract bug, prompting service halt.

Compensation promised for full losses, but repayment details remain unspecified, affecting user confidence.

Incident triggered broader chain pauses, delaying deposits on 11 networks and potentially impacting market liquidity.

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

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

That account was provided in a post from @near_intents published at 12:53 UTC. It was still the account’s only statement on the incident as of 13:15 UTC. Alex Shevchenko, who speaks for the product, and @NEARProtocol had not posted on it.

An earlier community alert, corroborated by a ZachXBT investigation and a TRM flow chart, put the same drain at more than $3.8 million and said the hot wallet had stopped processing transactions.

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

What left the NEAR Intents BSC hot wallet

The address identified as the destination of the outflows is 0x89fd1f5d9f185067a92493e43aa259ea4ab3ad37.

The flowchart shows 3,865,001 BSC-USD moving in seven transfers from a NEAR Intents-labeled wallet to that address on October 1. 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, identified in the alert, had stopped sending transactions. That indicates an operational stop, not 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 incidents 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 its post. Deposits and withdrawals were expected to remain paused for about 12 more hours on BSC, Polygon, TON, Optimism, Avalanche, Stellar, Monad, LayerX, Adi, Scroll and Plasma while the Omni fix was completed.

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 amount has been disclosed. 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 earlier, NEAR Intents was involved in blocking an attempted movement of funds linked to the Bitget hack.

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


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *