C✓WhyCoinMovesTHE EVIDENCE DESK
EN ▾
EN中文한국어日本語
← ARB event archive

Arbitrum council moved $30 million in Binance hack funds without the hacker's key

A 12-person committee briefly rewrote one of Arbitrum's core contracts to spend from an address it held no key for, then restored the code, CoinDesk reported. The council moved $30 million of Binance hack funds, the second time it has done so this year, according to the report.

Key facts

1 sourceMajor storyNew
Source published First received Updated UTC

Claims and open questions

Evidence strength Single source

Only one publisher so far. Another independent outlet or an official source would raise it.

ImportanceMajor story

Security topic

How recentVery recent

Fresh security news

What sources claim

  • CoinDesk reported that a 12-person committee briefly rewrote one of Arbitrum's core contracts to spend from an address it held no key for, then put the code back.
  • CoinDesk reported that the council moved $30 million of funds from the Binance hack.
  • CoinDesk reported that this was the second time the council took this action this year.

Still unresolved

  • Which specific core contract was modified and what code changes were made to enable the spend would need an official Arbitrum statement, governance post or on-chain transaction record to confirm.
  • Whether the recovered $30 million was returned to Binance, distributed to users or otherwise allocated would need an official statement from Arbitrum or Binance, or on-chain data, to confirm.

Evidence levels describe source coverage, not the probability that a report is true. Price moves and their timing cannot establish a cause; minute samples show an observed interval and alert thresholds are heuristics. Explanations are model-assisted, with citations and figures checked. Source titles stay in their original language; full articles are not republished.

Source evidence

1
CoinDeskNews publisher
Arbitrum’s council moved $30 million of Binance hack funds without the hacker’s key ↗

Published Nov 3, 2026, 05:25 · Received Nov 3, 2026, 07:37

Timing does not establish causation. Methods and limitations →

Recent Security events on other coins

Security →

Research for this archive