Maya Protocol, a cross-chain liquidity network modeled on THORChain's architecture, suffered an exploit on Thursday that drained approximately $1.7 million from its pools, according to a report by shattered.io. The attack triggered an immediate collapse in the protocol's native token, CACAO, which lost 88.7% of its value within hours of the breach becoming visible on-chain.

The exploit targeted Maya Protocol's core liquidity infrastructure. Maya operates as a decentralized exchange and liquidity protocol that enables cross-chain swaps without wrapped assets, using CACAO as its settlement asset across supported networks. A drain of this magnitude against the protocol's pooled capital directly undermines the collateralization that backs CACAO itself, which explains the severity of the token's decline relative to the size of the loss.

The 88.7% crash in CACAO far exceeds the proportional damage one might expect from a $1.7 million exploit alone. The divergence points to a loss of confidence in the protocol's solvency: in systems like Maya's, where native assets are minted and burned against pooled collateral, an exploit of the pools calls into question whether remaining CACAO holdings retain any meaningful backing. Liquidity providers holding pooled assets face parallel exposure, and positions in affected pools may be unrecoverable depending on which contracts the attacker drained.

The report from shattered.io did not specify the exact technical vector of the exploit, the attacker's wallet address, or whether the drained funds have been traced to any exchange deposits. On-chain investigators frequently track exploited funds through mixers or bridging services in the hours after such incidents, and recovery prospects for decentralized protocol breaches of this type are historically poor without a negotiated return.

Maya Protocol launched as a community-driven fork of THORChain, one of the earliest cross-chain swap protocols in the sector. It extended THORChain's design with additional chain support and modified economic parameters, building a liquidity network that relies on continuous deposit and withdrawal integrity to maintain its swap functionality. An exploit at the pool level forces the protocol's operators to confront a difficult operational question: whether to pause pools, coordinate a fork that restores pre-exploit balances, or attempt to continue operations with diminished collateral.

Each path carries costs. Pausing pools halts swaps and withdrawals for legitimate users but limits further drainage. A fork that reverts balances, an approach some protocols have adopted after major breaches, requires broad validator and liquidity provider coordination and can fracture the community. Continuing operations without remediation risks a deeper run on remaining liquidity as holders race to exit positions before the pools empty.

The CACAO token's 88.7% decline indicates that market participants priced in a near-total impairment of the protocol's backing. For a token whose fundamental value derives from its role as collateral in the swap system, a collapse of this scale effectively removes it from consideration as a settlement asset until the protocol demonstrates restored solvency.

The incident adds Maya Protocol to the growing list of cross-chain and decentralized exchange protocols hit by exploits. Attacks against DeFi infrastructure have drained billions of dollars across the sector since 2021, with cross-chain systems consistently among the most-targeted categories because their complexity multiplies the attack surface: multiple chains, multiple token standards, and bridge mechanics all introduce potential failure points that single-chain applications avoid.

For Maya's liquidity providers, the immediate priority is determining which pools the exploit affected and whether any portion of deposited assets remains withdrawable. For the protocol's developers and node operators, the coming days will likely determine whether the network continues operating in any form: an official incident report identifying the exploit vector, a remediation plan for affected liquidity providers, and evidence that unaffected pools retain intact collateral are the minimum disclosures needed to stem further erosion of trust.

No statement on user compensation, pool pauses, or a post-mortem timeline had been attributed to Maya Protocol's core team at the time of the shattered.io report. Given the protocol's decentralized governance structure, any remediation decision will depend on how quickly node operators and the community can coordinate a response — a process that competing exploits have shown can take days or weeks, during which remaining liquidity remains exposed.