--- title: Arbitrum Council Moved $30M in Binance Hack Funds Without the Hacker’s Key url: >- https://www.cryptocatalyst.news/articles/2026-11-03-arbitrum-council-moves-30-million-in-binance-hack-funds-without-the-hackers-key canonical: >- https://www.cryptocatalyst.news/articles/2026-11-03-arbitrum-council-moves-30-million-in-binance-hack-funds-without-the-hackers-key date: '2026-11-03T14:05:06.915628+00:00' category: ethereum tags: - arbitrum - binance - hack - governance - security source: CoinDesk source_url: >- https://www.coindesk.com/tech/2026/11/03/arbitrum-s-council-moved-usd30-million-of-binance-hack-funds-without-the-hacker-s-key publisher: CryptoCatalyst summary: >- Arbitrum’s 12-person council temporarily changed a core contract to move $30 million tied to the Binance hack without the address’s private key, then restored the code. Second such image: >- https://www.cryptocatalyst.news/images/articles/2026-11-03-arbitrum-council-moves-30-million-in-binance-hack-funds-without-the-hackers-key.webp generated_by: automated editorial pipeline --- # Arbitrum Council Moved $30M in Binance Hack Funds Without the Hacker’s Key A 12-person Arbitrum committee temporarily changed a core contract to move $30 million in funds linked to the Binance hack, despite not having the address’s private key. It then restored the code; the report says this is the second time this year the council has used this kind of intervention. ## Key takeaways - Arbitrum council moved $30M in Binance hack funds without the private key. - The committee temporarily changed a core contract, then restored the original code. - This is the council’s second such intervention in 2026. - Earlier in 2026, the council froze $71M from the Kelp DAO hack. Arbitrum’s 12-person council moved $30 million in funds tied to the Binance hack without the hacker’s private key. It briefly changed one of the network’s core contracts so it could spend from an address the committee did not control through an ordinary wallet key, then put the code back. The intervention shows that, in this case, a council could override the normal rule that only a private-key holder can authorize spending from an address. The source describes it as the second time this year the council has taken such action. ## How the council moved funds without the key A private key is normally the credential that authorizes transactions from a crypto address. Here, the committee temporarily rewrote a core contract—the code that helps govern how Arbitrum operates—to allow spending from the address. The available report does not provide further details about the contract change or where the funds went afterward. The council restored the original code after the move. That means this was a temporary intervention, not a permanent change to Arbitrum’s rules, based on the information provided. ## What this means for Arbitrum users The move highlights a trade-off in network governance: an organized committee may be able to respond to stolen funds, but the same ability can also override normal transaction controls. For users, the key question is not only whether funds can be recovered, but who has the authority to change a core contract and under what circumstances. This matters in the wider Binance hack story, where other responses have included stablecoin issuers freezing funds. Unlike a freeze imposed by an issuer on its own token, Arbitrum’s action involved temporarily changing core network code. The report does not say whether the $30 million was ultimately returned to its owner or how the council decided to act. This is not the first time Arbitrum’s governance has intervened in fund recovery. In May, Aave used an Arbitrum vote to attempt transferring $71 million in disputed ETH tied to a 2022 exploit. And in June, the Arbitrum Security Council froze $71 million from the Kelp DAO hack, the only portion of $293 million that remained recoverable after the hacker laundered the rest. ## FAQ ### How did Arbitrum move funds without the hacker’s key? A 12-person committee temporarily changed one of Arbitrum’s core contracts to authorize spending from an address it did not control with a private key. It then restored the original code. ### How much money did Arbitrum’s council move? The council moved $30 million in funds linked to the Binance hack. ### Does this mean Arbitrum can change transactions? The report describes a temporary change to a core contract that enabled this specific move. It does not establish that the council can change any transaction or explain the full limits on its authority. ## Source This article is a summary of reporting by [CoinDesk](https://www.coindesk.com/tech/2026/11/03/arbitrum-s-council-moved-usd30-million-of-binance-hack-funds-without-the-hacker-s-key), written by an automated editorial pipeline. See https://www.cryptocatalyst.news/editorial-policy. ## How to cite CryptoCatalyst.news, "Arbitrum Council Moved $30M in Binance Hack Funds Without the Hacker’s Key", 2026-11-03, https://www.cryptocatalyst.news/articles/2026-11-03-arbitrum-council-moves-30-million-in-binance-hack-funds-without-the-hackers-key