A severe MAPO bridge exploit sent Map Protocol’s native token into a near-freefall, wiping out 96% of its value after attackers allegedly used the Butter Network cross-chain bridge to mint an enormous amount of unauthorized supply.
The selloff was brutally fast. According to reported on-chain analysis, attackers minted a quadrillion unauthorized MAPO tokens, then pushed roughly 1 billion of them into Uniswap liquidity pools. Blockaid said the move drained about 52 ETH from those pools as the market struggled to absorb a supply shock far beyond the token’s legitimate circulation.
That combination — sudden inflation, immediate dumping, and thin on-chain liquidity — helps explain why MAPO fell from about $0.003 to nearly $0.0001 within hours.
Summary
How the MAPO bridge exploit unfolded
The central event was a Butter Network hack tied to the bridge layer, not a straightforward compromise of the MAPO token contract itself. The exploit allegedly let the attacker create unauthorized tokens through the bridge flow, overwhelming the existing supply and crushing price discovery almost instantly.
Blockaid said the attacker minted around 1 quadrillion MAPO, a figure that dwarfed the project’s reported legitimate supply of about 208 million. From there, roughly 1 billion MAPO were dumped into Uniswap liquidity pools, pulling out about 52 ETH in the process.
Unauthorized minting through Butter Network
The reported mechanism matters here. Map Protocol said the issue originated in the Solidity contract implementation, not from compromised keys and not from failures in its light client infrastructure.
That distinction is important because it narrows the problem to contract logic inside the bridge path rather than a broader breakdown of core cryptographic trust. In practice, the exploit hit a system that sits between chains, where message handling and validation are often the most fragile parts of the stack.
Blockaid’s analysis pointed to a Solidity-layer flaw in the bridge retry path. The firm said the exploit involved an abi.encodePacked collision across dynamic-bytes fields, allowing a manipulated retry message to be treated as authentic after an initial legitimate oracle multisig-signed message had already been submitted.
Why the supply shock hit price so fast
The market reaction was harsh because the exploit did more than steal assets. It created a supply event so large that it swamped the token’s normal trading structure.
When unauthorized tokens are minted and then rapidly sold into liquidity pools, buyers are suddenly pricing not just current damage but the possibility of more sell pressure ahead. That fear becomes even more intense when the attacker is still believed to hold a large remaining balance. As a result, the damage often appears as a fast collapse rather than a gradual decline, especially for tokens dependent on bridge-linked liquidity.
This is one reason the Map Protocol crash drew attention beyond its own ecosystem. It showed how a cross-chain token mint can turn a technical bug into an immediate market crisis.
What Map Protocol said about the flaw
Map Protocol later said the bug came from the Solidity contract layer. It explicitly said the incident did not stem from compromised keys or failures in the light client infrastructure.
That statement is a key part of the response because it separates bridge message execution from the project’s broader security architecture. It also signals that the protocol sees the root cause as a software implementation problem rather than a breakdown in custody or validator trust.
Contract-layer issue, not keys or light client failure
The project’s explanation lines up with the broader reporting around the exploit. Blockaid described the issue as a classic Solidity vulnerability involving multiple dynamic fields, rather than stolen private keys or broken cryptographic verification.
For users and market watchers, that matters because cross-chain systems often depend on layered trust assumptions. If the problem is at the contract layer, remediation can focus on code, migration, and exclusion of attacker-linked balances instead of rebuilding the entire trust model around key management or client verification.
Mainnet pause and migration
Map Protocol said it paused the mainnet and started a migration process after the incident.
The team also said a new contract address and an asset snapshot timeline would be announced separately. Tokens controlled by attacker-linked wallets are expected to be excluded from future conversion events and invalidated during the migration process.
That response suggests the project is trying to contain both the technical damage and the supply contamination caused by the exploit. In bridge attacks, that second part can be just as important as patching the bug itself.
Why the stolen MAPO may still matter
Even after the first dump into Uniswap, the incident may not be fully contained at the market level. The reported concern is simple: if a large quantity of unauthorized MAPO remains under attacker control, the risk is not limited to the initial drain of about 52 ETH.
Any remaining balance could continue to pressure other liquidity pools and exchange markets if it becomes tradable. That is why migration design, token invalidation, and wallet exclusions now matter as much as the original exploit analysis.
This is another reason the MAPO bridge exploit matters for DeFi users. Bridge attacks do not just hit protocol treasuries or smart contracts; they can directly distort circulating supply, liquidity quality, and price integrity. In a token-based ecosystem, that can reshape confidence long after the first exploit transaction is over.
A wider warning for cross-chain infrastructure
The MAPO bridge exploit lands amid a broader run of attacks targeting interoperability systems across decentralized finance.
Map Protocol connects Bitcoin with Ethereum, BNB Chain, Tron, and Solana, placing it in a part of crypto where cross-chain functionality is a feature but also a persistent security challenge. When bridges fail, the fallout tends to spread across chains, liquidity venues, and user trust all at once.
Recent reporting around other incidents has kept that pressure in focus. Earlier this week, Verus Protocol’s Ethereum bridge lost more than $11.5 million in an exploit tied to alleged forged cross-chain transfer instructions. Separately, TON-TAC, a bridge extension for The Open Network, said it recovered nearly 80% of the assets lost in its own $2.68 million exploit, though it remains paused pending an independent audit.
The pattern is hard to ignore. Bridge systems are supposed to make crypto more connected. However, each new exploit is a reminder that the messaging and validation layers between chains remain one of DeFi’s most exposed pressure points — and when they break, the price damage can arrive before a protocol has time to explain what happened.
