Hello, this is Nakajima, chief editor of BTC Macro Lab. Here is this week’s roundup. This time, we are doing a special on the biggest crypto hack in history, the one at Binance, which shocked the world.
We will follow the story in order, from October 29, when it happened, to today, Sunday, November 1. Then we will look at what it showed us about Japan, and at what problems remain. Here is the flow of this issue.
- What happened: a Thursday afternoon, and one laptop
- What the attacker knew: assets that can be stopped, and assets that cannot
- How the market moved
- The impact on Japan: domestic exchanges, and the Coincheck hack eight years ago
- The US debate: regulation and the Clarity Act
- Problems that remain, and what to watch next week
1. What happened: a Thursday afternoon, and one laptop
It began on Thursday, October 29, at around 4:20 p.m. US Eastern time. In Japan, that was around 5:20 a.m. on Friday, October 30.
A large amount of assets was pulled out of a hot wallet at Binance, the world’s largest crypto exchange, in a short period of time. A hot wallet is a storage location that an exchange keeps connected to the internet, used for withdrawals.
The way in is believed to have been one laptop. In Binance’s initial investigation, the laptop of an engineer who handles system development and operations was compromised. From there, the attacker may have gotten into the systems that run the service and sent out unauthorized withdrawal orders. Binance explained that it had found no evidence that the wallet’s private keys (the keys that open the storage) had leaked.
Later, a Binance co-CEO said the break-in point was not limited to the laptop. The attackers had also used a way of slipping past the approval controls, and a mechanism that erased their tools and traces.
CoinDesk and others report that the attack used an Ethereum feature called EIP-7702. It lets an ordinary wallet act with the help of a smart contract, which is a program that runs by itself. It is a convenient feature. According to the blockchain analytics firm Chainalysis, the attacker used it to make Binance’s hot wallet run software the attacker had prepared, and to move the assets to the attacker’s own addresses.
The damage grew by the day
The first reports said more than $2.5 billion. Then the tracking firm Arkham reported more than $5.7 billion, and Binance itself announced about $6.3 billion (around ¥976.5 billion). Chainalysis puts it at about $6.4 billion and calls it the largest crypto theft ever. The previous record was about $1.5 billion, at Bybit in February 2025, so this is more than four times as large.
The three days, day by day
- Thursday (29th): The attack started at around 4:20 p.m. By 5:14 p.m., freezes had begun. Binance stopped withdrawals. Its founder, CZ, said “it looks like a hack,” and that user funds were safe and that he expected them to be fully covered.
- Friday (30th): Bitcoin fell from the previous day’s high of $81,890 to as low as $76,301. Binance announced the damage at about $6.3 billion and said it had frozen about $3 billion of it. Several analytics firms pointed to the North Korean hacker group “TraderTraitor.”
- Saturday (31st): Binance said it had covered 90% of the stolen assets, up from 80% the day before. The same day, the FBI announced that North Korea was behind the attack.
- Sunday (today): Binance plans to reopen withdrawals.
2. What the attacker knew: assets that can be stopped, and assets that cannot
This is the part that made me think the most.
For stablecoins (crypto assets pegged to the value of a currency such as the dollar), such as USDT and USDC, the company that issues them can make the tokens at a given address unmovable. This is called a “freeze.” Bitcoin and ether (ETH), on the other hand, have no issuing company. So there is no one who can stop them.
The attacker knew this difference well. Of the $500 million in stablecoins taken, about $325 million was converted into ether in somewhere between 20 minutes and an hour. They moved the assets into ones that cannot be stopped before the freezes arrived.
So how did the side trying to stop them respond? Tether, which issues USDT, froze about $1.567 billion 37 minutes after the funds reached the attacker’s main wallet. Circle, which issues USDC, followed three minutes later with about $823 million. Ripple and World Liberty Financial joined in, and about $3 billion was stopped in total. That is nearly half of what was stolen.
I think this is a case where the nature of stablecoins paid off enormously. A stablecoin is designed so that its issuer can stop it when it matters. Because it is designed to be stoppable, authorities such as the US government find it easier to accept stablecoins as a dollar-linked means of payment. Bitcoin and ether have the advantage that nobody can stop them, and this time that showed up as the fact that nobody could.
But one criticism has come out here. It is the “double standard.”
In April, Circle’s CEO said USDC would be frozen only when law enforcement or a court instructed it. Yet this time, when Binance was hit, about $3 billion was frozen within hours. Experts point out that smaller victims get answers about court orders and legal constraints, while Binance got fast action, and they ask whether the standards are the same for everyone. The question is whether this quick response will become a precedent, or an exception limited to Binance’s size.
Where the assets that could not be frozen went
The assets that were not frozen remain. According to Decrypt, the attacker still holds more than 420,000 ETH and 18,270 BTC, about $2.4 billion in total.
The 18,270 BTC were gathered into one address in 11 transfers and, within minutes, split across 19 addresses: 1,000 BTC each at 17 addresses, and 832.5 BTC and 437.7 BTC at the other two.
The later movement of funds had its own pattern. According to Chainalysis, many addresses first received exactly one unit of TRX, the fee token of the Tron network, and then moved funds on. Thousands of transactions were repeated in the same way in a short time. The funds appeared to be spread out by a program rather than by hand, to make them harder to trace.
The FBI says the attacker is converting the stolen assets mostly into ether, and expects the cashing out to continue through DeFi (decentralized finance, financial services that run without an intermediary) and instant-swap services. It has asked exchanges and analytics firms to stop dealing with the attacker’s addresses.
3. How the market moved
Bitcoin
On Thursday, bitcoin had risen to nearly $82,000 on strong US GDP (gross domestic product) data. Then the Binance incident landed on top of that, and on Friday it fell to as low as $76,301. After that it traded around $77,000, and on Saturday afternoon it was near $77,400.
October is on track to end down 7.7%, which would be the worst October since 2014 according to CoinGlass.
But this fall was not caused by the Binance incident alone. On the same Friday, Intel said its fourth-quarter revenue outlook would come in below expectations, and its shares fell almost 30%, spreading the sell-off in AI-related stocks. Gold, which has been seen as a place to put money when stocks fall, also dropped to a one-year low. I think it is quite likely that these factors came together on the same day and set off a broad move to turn assets into cash.
Liquidations (forced closing of leveraged trades when prices move against the borrower) reached about $1.5 billion in 24 hours, and more than 80% of that was on the side betting on a rise.
ETFs
US spot bitcoin ETFs had taken in about $440 million over four straight days, Monday through Thursday. On Friday, they saw outflows of about $643 million in a single day. Money left main products at the same time, including IBIT, FBTC and ARKB. Total net assets fell below $100 billion.
The incident happened after US ETF trading had closed, so Friday was the first trading day on which ETF investors could react.
Still, bitcoin’s fall was only about 4% from just before the attack. According to Anchorage Digital, after past exchange incidents bitcoin fell 8.3% on average over 24 hours. This was about half of that. The bitcoin held by ETFs is not kept in exchange hot wallets. ETF investors suffered no direct loss, so I think it is natural to see the outflow as an emotional reaction to the incident. The market seems to be treating this as a problem of an exchange, and separating it from confidence in bitcoin itself.
Stocks and companies
Crypto-related stocks also fell sharply on Friday. Coinbase closed down 10.62%, and Circle, the stablecoin issuer, was down 9.3%. Coinbase had just reported earnings the day before.
Some companies are also reviewing the risk of the bitcoin they hold. Nasdaq-listed Next Technology Holding’s board approved selling or pledging about 5,833 BTC as collateral. The company’s bitcoin is not held at Binance. It still cited exchange vulnerabilities as a reason. There is also information that institutional investors are pulling assets off centralized exchanges.
India’s largest exchange, CoinDCX, put its futures market into a mode where positions can only be reduced, because Binance was one of the global liquidity providers it relies on. Exchanges are connected to each other, so an accident at one company reaches the trading conditions of others.
4. The impact on Japan: domestic exchanges, and the Coincheck hack eight years ago
What domestic exchanges did
In Japan too, there were moves right away.
Binance Japan announced on the 30th that no impact on customer assets had been confirmed at that point. Trading continues, but deposits and withdrawals of crypto are suspended for now, for safety checks. bitFlyer restricted transfers of crypto to Binance accounts until safety is confirmed. At the same time, it explained that its own systems and customer assets were not affected, and that customers’ crypto is kept in cold wallets isolated from the network and separate from the company’s own assets.
SBI Holdings announced that its subsidiaries’ exposure to Binance (their financial involvement) is limited at this point, and that there is no impact on consolidated results. SBI VC Trade and bitbank, both under SBI, are operating normally, and it says customer assets are not affected.
I think this announcement is very important. A Japanese company showed its own exposure, quickly and clearly, to an incident that happened overseas. What makes that possible is Japan’s system. Domestic exchanges are required to keep customer assets separate from their own, and to store them in cold wallets. Customer assets are protected, separated from the operator’s own business. I think SBI could say that customer assets were not affected precisely because this system is the foundation.
The Coincheck hack, eight years ago
Watching this incident, I think many people in Japan’s crypto industry remembered the Coincheck hack of eight years ago.
In January 2018, about ¥58 billion worth of NEM was stolen from Coincheck. The structure then was very similar to this one. Malware got into one engineer’s PC, and the assets in the hot wallet were drained from there. Eight years later, across that span of time, the same entry point and the same structure have appeared again.
What is different is the progress in defense over those eight years. Wallet management technology has advanced a great deal. In Japan too, after the Coincheck hack, exchanges were required to segregate customer assets and keep them in cold wallets. Binance was among the exchanges using the most robust setups in the world. It was still broken. North Korea’s attack capability had reached a level above eight years of defensive progress.
Japan has been targeted before. In May 2024, more than $300 million was stolen from DMM Bitcoin. The FBI and Japanese investigators attribute that to North Korean attackers. The method was to pose as a recruiter and send a rigged coding test to an employee of the wallet company Ginco.
The GMO case, and Japan’s decision
There is one more Japanese experience I want to tell you about: how Japan responded when GMO Group was hit by a cyberattack.
The attackers had a site where they published stolen customer information. Japan’s Ministry of Internal Affairs and Communications asked telecom carriers to block access to it. It was a forceful step, and a contested one because of its relationship with the secrecy of communications, and opinion was divided. The attackers’ domain was confirmed down on October 28.
In the Binance case this time, the US had no legal basis for the same kind of move, and its intervention came late. I think Japan’s decision is a case worth showing to the world.
Japan learned from past incidents, and the government did what needed to be done. The US has also made progress in many ways, in technology and in business. But on national policy for incidents like this, it has still not come together. It is unfortunate that the Clarity Act has not passed.
5. The US debate: regulation and the Clarity Act
In the US, there are moves to use this incident as material for the debate over regulation.
CFTC (Commodity Futures Trading Commission) Chair Selig said on the 30th that the Binance hack “proves exactly our point.” His explanation is that offshore exchanges, which are not regulated, lack the protections that exist in US financial markets.
The CFTC is preparing a path for exchanges, including offshore ones like Binance, to register with the CFTC voluntarily. Registered exchanges would come under a framework covering cybersecurity, customer protection and custody of assets. But registration is not mandatory. Requiring all exchanges would need legislation from Congress. The comment period on the proposed rules runs until December 14.
The other issue is the Clarity Act, the comprehensive bill that sets rules for the crypto market. Sen. Lummis argues that if the bill had been passed, companies acting at the request of law enforcement would have legal protection when freezing suspicious transactions.
Amanda Fischer, a former chief of staff at the SEC, pushed back that the bill requires stablecoin issuers to freeze on the basis of a court order. Patrick Wilson of the Solana Policy Institute replied that the bill contains a provision that protects issuers from civil lawsuits when they freeze voluntarily and temporarily, and that no court order is needed.
The bill stalled at a Senate vote on September 15, at 49 to 50, short of the 60 votes needed to move forward. The points of dispute were ethics rules for government officials on crypto, and yield on stablecoins.
In fact, two days before the incident, on October 27, Treasury Secretary Bessent said at an event hosted by Ripple that he was “disappointed” the Clarity Act was stalled, and that the Treasury would bring together the SEC and the CFTC to fill the gaps in regulation. His stance was to move forward even without a law.
Under the previous Biden administration, the SEC often focused on enforcement, such as suing exchanges for securities violations. Now the CFTC is offering a path to registration to draw exchanges into the US framework. Binance’s former CEO pleaded guilty in 2023 to inadequate anti-money-laundering controls. That same exchange is now being used as an example of why regulation is needed.
6. Problems that remain, and what to watch next week
Three days in, Binance has covered 90% of the stolen assets. Ten major assets are said to fully back user balances. The remaining 10% is in illiquid tokens, which Binance is buying up on the market and over the counter. The money comes from its own funds, part of its user protection fund (SAFU) and the surplus in its futures insurance fund. It also says it has set aside more than $6.34 billion of its own funds for compensation.
At the same time, this incident leaves several problems.
- Where the stolen $2.4 billion goes. The bitcoin and ether that could not be frozen: where will they move next, and how? The FBI and analytics firms are continuing to trace them.
- The standard for freezing. On what standard, and for which victims, will issuers freeze? The double-standard criticism needs an answer.
- Control of signing and approval at exchanges. How many layers can an exchange that holds customer assets put on signing and approval? The incident shows the attacker getting in from one PC and slipping past the approval controls.
- Trust in proof of reserves. The wallet that was hit was on a list Binance had published to show that “customer assets are backed one to one.” A complete proof using zero-knowledge proofs (a technique that shows a calculation is correct without revealing what is inside) is expected around November 3. That will show whether trust returns.
- US legislation. How far will the CFTC’s proposed rules and the Clarity Act go?
What to watch next week
These are the things that will clearly continue next week.
- Binance’s reopening of withdrawals, and proof of reserves (around November 3). Will Sunday’s reopening go as planned? Will users come back?
- The US midterm elections on November 3. The result will bear on whether the Clarity Act moves again.
- ETF flows. Monday’s flows will show whether Friday’s outflow was a one-time event.
- Developments in Japan. Any further disclosure from SBI’s review, the resumption of deposits and withdrawals at Binance Japan, and announcements from domestic companies.
- Whether the roughly $3 billion that was frozen is actually returned.
This incident made us think again about what it means to leave assets at an exchange, and about the difference between assets that can be stopped and assets that cannot. Japan has built a great deal on the experience of the Coincheck hack eight years ago. Today, that experience is serving as a reference point in the world’s debate.
Thank you for reading to the end. Next week too, we will bring you the week’s important moves, as the chief editor’s choice.
This article is provided for information only and does not recommend buying or selling any crypto asset or financial product. Please check primary sources and official announcements and make your own decisions at your own responsibility. We use AI in part of our work.