A DeFi protocol has just lost $3.8 million to a critical vulnerability — and the timing could not have been worse. NEAR Intents, which had only just stepped in to help manage the fallout from the Bitget security breach, found itself squarely in the crosshairs of hackers. An internal flaw that had slipped under the radar was all it took to bring everything crashing down.
The platform confirmed the incident and announced full compensation for all affected users. But behind that promise, the broader question of interoperability protocol security is resurfacing — with a particular urgency.
A Bug in Deposit and Withdrawal Mechanics at the Root of the Exploit
According to information shared by the NEAR Intents team, the exploit originated from a bug directly affecting the platform’s deposit and withdrawal mechanisms. This flaw, likely present in the codebase for some time, allowed an attacker to drain funds without triggering the usual security alerts.
This type of vulnerability — often described as a reentrancy bug or a logic flaw in liquidity flow handling — is among the most feared in the DeFi ecosystem. It does not require the compromise of private keys: exploiting an inconsistency in smart contract logic is enough to repeatedly or unauthorizedly siphon funds. The $3.8 million extracted points to an exploitation window wide enough for the attacker to operate without being stopped in time.
The platform stated it has identified the attack vector and is working on a fix. It has also committed to reimbursing all affected users in full, though the exact terms and timeline for that compensation have not yet been disclosed.
The Link to the Bitget Hack: A Coincidence Worth Questioning
What makes this incident particularly striking is its immediate context: NEAR Intents had just been involved in helping manage the consequences of the Bitget hack, the centralized exchange that had itself suffered a significant attack. Did that operational involvement expose the protocol to heightened scrutiny from malicious actors? The question is absolutely worth asking.
In the crypto ecosystem, periods of crisis on one protocol or platform regularly draw hackers’ attention toward the entities operating in its orbit. Teams mobilized on an emergency basis, unusual fund flows, cross-protocol connections activated under degraded conditions — all of these factors can create blind spots in security. NEAR Intents appears to have paid the price for that involuntary exposure.
This chain of events echoes a pattern already seen across the industry: interoperability and liquidity routing protocols — inherently connected to multiple sources — represent prime targets for sophisticated attackers. Their technical complexity and cross-chain interactions multiply the potential attack surface considerably.
What Comes Next for NEAR Intents and Its Users?
The team’s immediate priorities are twofold: securing the protocol through an emergency patch and delivering on its compensation promise. On that second point, NEAR Intents‘ credibility will be judged directly by the speed and transparency of the reimbursement process. Affected users are waiting for concrete action, not just announcements.
For the broader NEAR Protocol ecosystem, this incident comes at a sensitive moment. The network is working to establish itself as a serious infrastructure layer for DeFi and cross-chain interoperability. An exploit of this scale — even if handled correctly in the aftermath — leaves a mark on the protocol’s security perception and could slow the institutional adoption the team has been actively pursuing.
Independent security audits and active bug bounty programs remain, to this day, the strongest defenses against this kind of scenario. The NEAR Intents incident serves as yet another reminder that in DeFi, no protocol is immune to an undetected vulnerability — especially when operating under pressure.
