The Arbitrum Security Council froze 8,425 ETH and 74,559,805.2 ARB on Arbitrum One from an address identified with the Binance exploit on 30 October 2026, using a temporary upgrade to the Ethereum inbox contract. The funds can only be moved by an ArbitrumDAO governance vote, and the notice sets no date for one.
The Arbitrum Security Council's emergency action of 30 October 2026 froze 8,425 ETH and 74,559,805.2 ARB held on Arbitrum One by an address identified with the Binance exploit. @Arbitrum posted the notice to the Arbitrum forum on 30 October 2026, and the post carries no replies. It matters because the Security Council moved the funds through a temporary upgrade to a live Ethereum contract that let it impersonate the address holding them, and because the funds can now only be moved by an ArbitrumDAO governance vote.
0x0000000000000000000000000000000000000DA0 on Arbitrum One.sendUnsignedTransactionOverride, which imitates the structure of a standard cross-chain transaction with the ability to impersonate the transaction sender.0xb69c81774f507d46ce776aeaed8b4d31df96dd66ce6fd05073481011835355d6, which Etherscan shows as successful, at 00:08:35 UTC on 30 October 2026.The notice gives its reason and its scope in one line: "Funds associated with the Binance exploit are frozen on Arbitrum One. No other user's funds or applications were affected."
The action was completed on 30 October 2026, and the forum thread carries one post describing it, with no replies and no vote. The frozen balance of 8,425 ETH and 74,559,805.2 ARB sits at 0x0000000000000000000000000000000000000DA0. The notice says the funds can only be moved by an ArbitrumDAO Governance vote, which will be coordinated with relevant parties, and it names no date for such a vote.
The agenda for the 3 November 2026 governance call, posted by @OpCo on 2 November 2026, lists the emergency action under quick updates. None of the on-chain or off-chain AIPs on that agenda concerns the frozen funds, so what remains open is the vote that would decide where they go.
This page was researched from Alphaday’s DAO proposal and governance forum feeds. They are open: free, no signup, no key.
Start building with the DAO proposals API
A 15-minute recipe: forty lines and a cron entry.
The same feeds as tools, for Claude, Cursor and any MCP client.
The discussion threads that come before the votes.
Stage and vote as read on 2 November 2026. Proposals move after a page is written; the forum thread and the vote have the current state. Quotes are from the posts linked beside them.