Avalanche Safe Loses $7.45M to Misconfigured Approvals; MEV Bot Front-Runs Exploit

Avalanche Safe Loses $7.45M to Misconfigured Approvals; MEV Bot Front-Runs Exploit


A trading team’s 2-of-7 Safe multisig on Avalanche saw an attempted drain of roughly $7.45 million after months-old unlimited token approvals pointed to an empty contract address that an attacker later claimed. 

An MEV bot front-ran the attack in the same block, captured the assets, and entered on-chain talks to return most of the funds in exchange for a bounty. The Safe owners later confirmed an offer of 42,500 WAVAX, valued at about $371,000.

Unlimited token approvals to an empty Avalanche address enabled a sweeper contract to claim $7.45 million from the Safe.

An MEV bot front‑ran the attack, seized 3.09 M USDC and other assets, then proposed a 5‑10% bounty.

Safe owners offered 42,500 WAVAX (~$371k) as bounty, pending on‑chain agreement to return most funds.

Defimon Alerts, the DeFi monitoring service that surfaced the incident, said it detected the activity on October 26 at 13:00:23 UTC. The service has previously identified similar Safe-related issues across chains.

Misconfiguration Rooted in Cross-Chain Address Collision

The vulnerability dates to a batch of approvals executed on March 7, 2026, at 16:10 UTC. The Safe granted unlimited spending rights for WAVAX, USDC, WETH.e, and BTC.b to the address 0x3725bd4d175283108156c3f15f86e1c51266155d. On Base, Arbitrum, and Ethereum that address hosts the team’s pool contract. On Avalanche the same address remained empty: it is the deterministic output of Safe’s public CreateCall factory on its 13th deployment, and CreateCall had never been used on the chain. The approvals were never revoked.

Because the address could be claimed by anyone, a fresh externally owned account used the Safe singleton factory to deploy CreateCall, ran 12 throwaway deployments to advance the nonce, and then placed a sweeper contract at the target address. The sweeper was designed to pull every approved balance from the Safe. The original attack transaction, viewable on Snowscan, ultimately reverted after the MEV bot moved first.

The episode illustrates a practical risk for teams that reuse deterministic addresses across chains while leaving high-value approvals in place. Infinite approvals to an address that is only meaningful on some networks effectively create a standing authorization that can be exercised the moment the address is claimed on an under-used chain. 

MEV Front-Run and On-Chain Bounty Negotiation

An MEV bot submitted a competing transaction that executed ahead of the attacker’s in the same block. It extracted 3.09 million USDC, 350,400 WAVAX, 182 WETH.e, and 10.79 BTC.b. The bot has described itself as a whitehat and posted an on-chain message offering to return the funds to a designated address while requesting a 5–10 percent bounty. The seized assets remain at 0x11eb9b677510e2594857f4d137fd12a7fef39bc5 pending resolution.

Defimon Alerts later reported that the Safe owners offered a bounty of 42,500 WAVAX. A follow-up transaction on Avalanche contains an input-data message confirming the terms: the parties agreed that the bot may keep 42,500 WAVAX if it proceeds with the remaining transfers. The message appears in the transaction details recorded on October 27.

Separately, the same operator maintains Safes on other networks. Beginning at 13:48 UTC on October 26, signers moved assets out of Safes on HyperEVM, Base, Robinhood Chain, BSC, and Ethereum into a single new address, 0x70d54baf9ffa48b8fe4e843774a44e24ff452099, which now holds approximately $38.7 million.

The case follows a pattern seen in other recent Safe incidents in which MEV searchers have front-run exploit attempts, as documented in coverage of an earlier Ethereum Safe drain and of access-control issues in custom Safe modules. Avalanche’s growing DeFi activity, including expanded lending markets, has increased the stakes of such configuration mismatches.

As of October 27 the negotiation continues. The MEV bot has indicated willingness to return the bulk of the assets once the bounty is settled, while the Safe owners have responded with a concrete WAVAX-denominated offer. Until the transfers complete, the $7.45 million remains under the bot’s control. The team’s prompt consolidation of assets from other chains appears to have limited further exposure. The outcome will hinge on whether the on-chain agreement is executed as described in the latest messages.

Also read: Ethereum Developers Merge Patch for Bug That Put Staking Deposits at Risk


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *