NEAR Intents, the cross-chain settlement primitive built on NEAR Protocol, lost approximately $3.8 million in an exploit reported by cryptopolitan.com. The incident landed within days of the same infrastructure declining to process roughly $50 million in proceeds that reporting linked to attackers of crypto exchange Bitget.

The pairing of the two events — a defensive refusal followed by an offensive loss of its own — is the central operational story. For an emerging settlement layer whose value proposition depends on both uptime and integrity, the sequence complicates the platform's near-term narrative.

What is NEAR Intents?

NEAR Intents is a solver-based settlement system that lets users express a desired outcome, typically a cross-chain swap, and lets a competitive network of market makers fulfill it. The design abstracts away bridging, gas, and chain selection, and has positioned the protocol as a flagship product of NEAR's broader chain-abstraction push.

The architecture shares a threat model with peer systems including THORChain, Wormhole, LayerZero and Across: each aggregates liquidity and routes value across chains, exposing them to smart-contract bugs, solver collusion, oracle manipulation, and money-laundering pressure.

Why the timing matters

The cryptopolitan.com report frames the $50 million Bitget-linked sum as funds that NEAR Intents operators actively refused to settle. The decision, if confirmed, would mark a notable enforcement action by a protocol whose peers have historically struggled to block illicit flows in real time.

The subsequent $3.8 million loss, by contrast, lands on the defensive side of the ledger. A successful exploit inside that same enforcement window raises questions about the maturity of the platform's monitoring and incident-response stack, and about the trade-off between building blocklists for known-bad addresses and securing the underlying solver and settlement contracts.

What the reporting does not specify

The available cryptopolitan.com coverage does not detail the attack vector, the on-chain address or addresses involved, or any recovery effort. It does not name a perpetrator, provide a transaction-hash trail, or quantify the share of user funds versus treasury funds in the loss. The publication likewise does not confirm whether the $50 million Bitget figure has been validated by Bitget itself, by a blockchain analytics firm, or by NEAR Intents operators.

Until a post-mortem is published by the NEAR Intents team, the exploit will be tracked primarily through third-party reporting and any subsequent on-chain analysis. That gap matters for institutional integrators and market makers evaluating whether to continue routing volume through the platform.

Market-structure context

NEAR Protocol has spent the past year marketing Intents as its primary entry point for institutional cross-chain execution. A $3.8 million loss is not material relative to NEAR's token market capitalization, but the optics of an exploit arriving immediately after a public refusal of a much larger sum will weigh on partner conversations.

Competing intent-based and cross-chain protocols have absorbed eight-figure losses in recent quarters, and the sector's security record remains an active diligence item for custodians, market makers and foundations. NEAR's developer community, which has historically been responsive to disclosed vulnerabilities, will be the audience to watch for the technical write-up.

What to watch next

A formal post-mortem from the NEAR Intents team, identifying root cause, remediation steps and any user compensation, is the first concrete milestone. Confirmation from Bitget or from a recognized blockchain analytics firm on the $50 million figure would clarify whether the rejected funds are tied to a specific disclosed exchange breach. Until both land, the episode will be cited in industry security roundups as a case study in the operational cost of being both a settlement rail and a real-time enforcement gate.