The Binance hack has given CFTC Chairman Michael Selig a new argument for federal oversight of offshore crypto exchanges. Speaking to CNBC on October 30, he cited the roughly $6.4 billion theft to support his agency’s proposed crypto-market rules, according to Decrypt.
Why it matters
Selig argues that offshore exchanges need safeguards comparable to those in US financial markets. Binance’s expanding account of the breach also raises a narrower question: whether the laptop vulnerability he described adequately explains an attack that the exchange says involved additional breach points.
What we know about the Binance hack
In its October 30 report, Decrypt reported that Selig said the attack “proves our exact point” about crypto-market regulations proposed earlier that month. He described a “federal option” under which offshore venues could register with the CFTC and face cybersecurity standards applied in US financial markets.
Selig attributed the incident to a vulnerability he believed was introduced through someone’s laptop, rather than a failure of Ethereum or its smart contracts. Binance initially pointed to a compromised DevOps engineer’s laptop, but said on October 30 that its investigation had uncovered “additional points of breach,” Decrypt reported.
CEO Richard Teng called it “a more complex attack process” that “did not simply use one engineer’s permissions.” Those statements complicate the laptop-focused explanation without supplying a complete alternative account of how the attackers obtained access.
How the Binance hack reached an on-chain wallet
According to Decrypt, the attacker used Ethereum’s EIP-7702 feature, which allows ordinary wallets to run smart-contract code, to turn a Binance hot wallet into a “sweeper.” The report identified 50 pre-signed authorizations used to drain the wallet’s assets.
Decrypt reported that TRM Labs viewed the broader breach as pointing to a compromise of Binance’s signing infrastructure rather than a weakness in a blockchain. Its account of the signing-infrastructure assessment distinguishes that suspected compromise from the use of an Ethereum feature during the attack.

What is still unclear
The October 30 report does not provide a complete sequence of the compromises or describe each additional breach point Binance identified. It therefore supports a limited conclusion: Binance’s investigation extends beyond the initial account of one compromised engineer’s laptop.
The regulatory question is also unsettled. Decrypt reported Selig’s case for US-style safeguards, but did not establish that the proposed rules would have prevented this theft. His remarks explain the policy argument, not a demonstrated security outcome.
According to Decrypt, the Secret Service and FBI have opened an investigation. The outlet also reported that TRM Labs and Chainalysis tied the theft to North Korea’s TraderTraitor group. That identification is attributed to the two blockchain analytics firms.
Decrypt also reported that Binance had set aside $6.34 billion to cover losses and assured users their assets were safe. The report records the exchange’s response, but does not provide a detailed account of how that allocation would be administered.
What the reported figures show
The approximately $6.4 billion theft and Binance’s $6.34 billion allocation describe different measures. The first is the reported scale of the attack; the second is the amount reportedly set aside to cover losses. Neither figure, by itself, explains the attack’s technical sequence.
| Measure | Reported figure | Context | Source |
|---|---|---|---|
| Theft | About $6.4 billion | Reported attack size | Decrypt |
| Loss allocation | $6.34 billion | Set aside by Binance | Decrypt |
| Pre-signed authorizations | 50 | Used in the wallet-draining operation | Decrypt |
The authorization count describes part of the on-chain operation, not the number of attackers or compromised employees. The report does not establish either of those totals.
Selig emphasized both the speed of crypto transfers and the possibility of tracing them. He said attackers can route funds through obfuscation tools such as Tornado Cash, while arguing that on-chain transaction records still give regulators an investigative advantage. That is his assessment of traceability, not a report that the stolen assets have been recovered.

What it means for investors
The Binance hack highlights the distinction between blockchain integrity and the security of an exchange’s asset controls. The reported theft did not expose a flaw in Ethereum itself, according to Decrypt, yet assets were drained from a Binance wallet. Binance’s assurances about customer assets remain statements by the exchange.
For the policy debate, Selig’s comments form part of a broader CFTC effort. According to Decrypt, the agency has pursued crypto rulemaking while the Clarity Act has stalled in the Senate. The outlet places his remarks within that effort to bring crypto exchanges under federal oversight.
Further disclosures about the additional breach points and the possible signing-infrastructure compromise could help clarify the security failure. Comparing those findings with the proposed requirements would be more informative than assuming that registration alone would have prevented the attack.
Bottom line
Selig is using the Binance hack to argue for bringing offshore exchanges under US supervision. The reported evidence does not establish that his proposed framework would have stopped this attack. Binance’s expanded account makes the distinction important: the policy argument is clear, but the technical explanation remains incomplete in the published report.
Sources
This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrencies are highly volatile; always do your own research before investing.

