NEAR Protocol's cross-chain swap layer NEAR Intents restored service after an exploit drained approximately $3.8 million, with losses confined to USDT liquidity bridged through BNB Smart Chain, CoinMarketCap reported on Tuesday.

What is known

According to CoinMarketCap, the attacker extracted USDT from a settlement route connecting NEAR's solver layer to USDT issued on BNB Smart Chain. The protocol's operators paused the affected corridor, and full service has since resumed. NEAR-native assets and settlement legs on other chains recorded no losses, which kept the incident's perimeter tight.

How NEAR Intents works

NEAR Intents operates as a solver network — a competitive market-making layer that lets users request cross-chain swaps without specifying an execution route. Professional and institutional liquidity providers, called solvers, compete to fill those requests, posting collateral on NEAR and delivering the requested asset on the destination chain.

Settlement against destination chains flows through dedicated corridors that lock value on the source chain and release equivalent value on the target. The BSC-USDT route functions as one such corridor — connecting NEAR's solver layer to the largest dollar-denominated stablecoin pool on BNB Smart Chain.

Why a contained perimeter matters

The $3.8 million loss does not directly threaten NEAR Intents' broader market position. Three factors limit the spillover:

• Single-corridor containment. The exploit touched one settlement leg, not the solver layer or order-book logic.
• Stablecoin-only loss. Extracted value sat in USDT on BSC, not in native NEAR or other chain-native liquidity.
• Functional restoration. Service returned after a brief suspension, suggesting the operators could isolate and patch the route.

A contained settlement-layer incident of this size is unlikely to displace routing volume away from NEAR Intents. The protocol still processes a meaningful share of cross-chain stablecoin flows that compete with bridge stacks built on Wormhole, LayerZero and Across.

What remains undisclosed

The CoinMarketCap report does not name the technical vector. NEAR has not, in publicly available materials, published:

• A post-mortem detailing the specific contract or signer compromise
• A reimbursement plan covering the $3.8 million loss
• An external auditor assignment to review the affected corridor

These omissions leave three operational questions open. Did the breach stem from a smart-contract vulnerability, an oracle manipulation, or a compromised signer? How will the protocol cover losses across treasury reserves, insurance pools, or solver collateral? What corridor-level monitoring will the team deploy to shorten detection windows going forward?

What to watch

Recovery volumes on the BSC-USDT corridor over the next 30 days will indicate whether institutional solvers treat the event as a one-off settlement-layer failure or as a reason to reroute volume through competing bridge stacks. A NEAR Foundation post-mortem and any third-party audit findings will determine whether the $3.8 million loss remains an isolated corridor breach or expands into a structural trust question for solver-based routing across multi-chain stablecoin flows.