The Binance Hack reports and the Ether spot print are not the same record. Tree News posted a transaction hash at 20:41 UTC on 29 October 2026. The Etherscan page for that hash shows a transf
The Binance Hack reports and the Ether spot print are not the same record. Tree News posted a transaction hash at 20:41 UTC on 29 October 2026. The Etherscan page for that hash shows a transfer of 167,464.25 ETH from the wallet labeled Binance 14, timestamped 20:24:23 UTC. Nebraskangooner, at 20:51 UTC, printed a different fact: Ether from $2,335 to $2,255 in the prior hour. A wallet debit and a spot print can share an hour and still be different documents. This record does not say the coins were sold. It does not say they were not sold. No post opened here showed that next step.
The spot print is the smaller document, and it is not a BNB percent. None of the posts opened for this piece printed a BNB percent beside the Ether line, so this article does not invent one and does not rank Ether against the exchange token. Nebraskangooner put Bitcoin beside Ether, $80.8k to $78.8k, and stopped there. The Kobeissi Letter at 20:55 UTC said Ether had fallen below $2,250, which is not the sentence "$2,335 to $2,255." The price change and the wallet debit stay apart. FinanceFeeds has already published the incident writeup. This article is the Ether price change that had already printed.
Nebraskangooner's 20:51 UTC post calls a Binance incident possible and unconfirmed. It says about $2.77 billion had just left Binance wallets across five chains, reportedly through a contract call funded by Tornado Cash, and then gives the market line: Bitcoin $80.8k to $78.8k, Ether $2,335 to $2,255. The close is a direct instruction. "Be cautious until Binance confirms."
That Ether line is a path, not a percent. The post does not say what $2,335 to $2,255 is in percent terms, and this article does not add a percent the account did not print. It also does not say the path was the low, the close, or an exchange's official one-hour change. It says the market was already reacting, and it prints those two Ether numbers.
Four minutes later The Kobeissi Letter said Bitcoin had fallen below $79,000 and ETH had fallen below $2,250 "as the selloff in technology stocks deepens." The cause in that sentence is the stock selloff. Nebraskangooner's cause, four minutes earlier, is the possible incident. The Ether thresholds do not match either. Below $2,250 is not $2,255. Below $79,000 is not $78,800. Both posts are in the file. They are not blended into a third print.
The Kobeissi post carries two chart images. The Ether image is labeled Ethereum / U.S. Dollar. Its header shows an open near $2,262.97, a high near $2,263.05, a low near $2,260.78, and a last near $2,261.39, with a change of $1.62, or 0.07 percent. That 0.07 percent is the header. It is not the drop from $2,335, and it is not a reason to call the hour a 0.07 percent move. The candles on the same image show a much larger drop than $1.62, and the post text says Ether fell below $2,250. Text and header on one post disagree. The Bitcoin image prints a last near $79,014.93, which is not "below $79,000." Same split, different coin. Bitcoin is here only because those posts printed it beside Ether.
I opened the transaction hash from the Tree News post on Etherscan before using the ether amount in this record.
Tree News at 20:41 UTC said its system had flagged a possible theft from Binance hot wallets, "withdrawing billions in over 60 tokens to an address funded by Tornado Cash," sixteen minutes earlier, with details still unclear. The post prints the hash 0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3.
The Etherscan page for that hash titles the action as Binance 14 transferring 167,464.25 ETH to the address tagged Binance Hot Wallet Exploiter 2. Status is Success. The timestamp is 29 October 2026, 20:24:23 UTC. A tooltip on the rounded amount reads 167,464.247856. An internal-transaction line reads 167,464.247856558836135296 ETH from Binance 14, 0x28c6c06298d514db089934071355e5743bf21d60, to 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c.
The page shows $382,938,820.93 beside 167,464.25 ETH, and $382.93 million beside the longer internal amount. That dollar mark is the explorer's conversion when the page was opened. It is not Nebraskangooner's $2,335, and it is not a trade ticket. Treating it as the spot print would mix a wallet valuation with a market quote.
The same page shows this warning: "Although one or more Error Occurred [execution reverted] Contract Execution Completed." The status above the warning is still Success, and the transfer line is still on the page. The warning is not turned here into a claim that the ether stayed put. The transfer line is not turned into a claim that the ether was sold into the $2,255 print. Both lines are on the page. The sale, or the absence of a sale, is not.
The image on that Tree News post is a separate card. It reads "Binance Hot Wallet Drained of About $2.53B in 60+ Tokens on Ethereum, Suspected Key Compromise," with 21:24 on the card. The post is timestamped 20:41 UTC. About $2.53 billion on an Ethereum card is not Nebraskangooner's about $2.77 billion across five chains, and it is not The Kobeissi Letter's about $2.8 billion across five blockchains. An Ethereum total and a five-chain total do not have to match. These do not. They stay separate.
The word was doing too much work on Thursday.
One use is from the day before, and it is a fund-share print. Wu Blockchain, citing SoSoValue, posted that U.S. spot Bitcoin ETFs recorded $137 million of net inflows on 28 October, led by BlackRock's IBIT at $136 million, and that spot Ethereum ETFs saw $21.41 million of net outflows. The headline on that post rounds the ether side to $21.4 million. The body says $21.41 million. This article uses the body figure. FinanceFeeds recorded that 28 October fund tape separately. A creation or redemption of ETF shares is not a debit from an exchange hot wallet, and it is not Thursday night's spot print.
The second use is the hot-wallet line: 167,464.25 ETH at 20:24:23 UTC, inside a transaction that also moved other tokens. That is an on-chain transfer between labeled addresses. It is not a statement about the ETHUSDT book.
The third use is the spot path. One post says $2,335 to $2,255. Another says below $2,250. The chart header on the second post is near $2,261.39. Those are quotes. They do not name a seller, and they do not identify the coins from Binance 14.
A desk that adds the ETF figure, the wallet debit, and the spot drop into one line about Ether "leaving the market" has combined three measurements. The Binance Hack file can hold all three only if the labels stay on them.
At 21:05 UTC Tree News posted: "TETHER FREEZES $971M USDT IN LIKELY BINANCE HACK, WITH NO UPDATE FROM BINANCE STILL."
At 21:14 UTC The Kobeissi Letter posted that Tether had frozen $971 million of USDT linked to a suspected Binance hack, that Binance wallets had seen a $2.8 billion outflow across five blockchains, and that Binance had yet to comment.
At 21:15 UTC Changpeng Zhao, posting as CZ, wrote: "User funds are safe! It does look like a hack on Binance. Appreciate the quick freeze from Tether (~$971m) and Circle (~$823m). I don't manage Binance (.com) anymore, but as a shareholder, I expect all user funds will be fully covered." He was quoting the 21:05 Tree News line. The Circle figure is in his post. It is not in the Binance account post below.
At 21:26 UTC Tree News posted a different Tether figure: "ARDOINO: TETHER FROZE MORE THAN 1.567B USDT: BBG." That is a Bloomberg attribution, as Tree News printed it. This article did not open a Bloomberg page, and it did not open an Ardoino post from Thursday night with those words. The 1.567 billion figure disagrees with the $971 million figure in the 21:05 post, the 21:14 post, and CZ's post. The disagreement stays. It is not averaged.
A freeze is an issuer blacklist. It is not an Ether price. Tether can freeze USDT. Circle can freeze USDC. Neither set the ETHUSDT quote. FinanceFeeds has covered earlier Tether blacklists that were also address-level actions, not spot quotes. Thursday's freeze posts are in this Ether file so a reader does not book $971 million, or 1.567 billion, as the Ether move.
The gap between the founder and the exchange account is the operational fact, and it is already on the posts.
CZ says it does look like a hack, says user funds are safe, thanks Tether and Circle, and says that as a shareholder he expects users to be fully covered. He also says he does not manage Binance.com. An expectation is not a draw on a reserve. The post does not say a fund was used that night.
The Binance account posted at 21:29 UTC: "Our teams are aware of reports of a potential security issue and are actively investigating. User funds are completely safe. Our security teams are reviewing all relevant information with urgency, and we will provide updates through official Binance channels as soon as we have." The sentence ends on "as soon as we have," then a link. The image is a logo card that says ANNOUNCEMENT. It does not finish the sentence. The post says "potential security issue." It does not say hack. It says user funds are completely safe. It does not mention Tether, Circle, SAFU, or an ether amount.
Nine minutes earlier, at 21:20 UTC, The Kobeissi Letter said Binance had responded to a suspected potential $2.8 billion hack, and attached a screenshot. The screenshot is worded as a Binance statement, and it is not the 21:29 text. It says the team has not confirmed any impact to user funds, that updates will follow verified information, and that users should avoid unofficial links and requests for account information. "Not confirmed any impact" is not "completely safe." The screenshot and the later post disagree. At 21:14 UTC the same letter had said Binance had yet to comment. The account post opened here is 21:29 UTC, after both lines.
FinanceFeeds has described the SAFU reserve before, including its use after an earlier hot-wallet loss. The Thursday posts opened here do not say the reserve was drawn. CZ said he expects coverage. Binance said it was investigating and that user funds are completely safe. Those are the words. They are not a price.
The chart is ETH/USDT 5-minute closes from the Binance public market API, from 18:00 UTC on 29 October 2026 through the latest closed bar when the file was saved. The dashed line is 20:24 UTC, marked outflow reports, because that is the Etherscan timestamp. The closes are not the prose prints. If a close on the chart is not $2,335, $2,255, or "below $2,250," the chart is not a correction of the post, and the post is not a correction of the chart.
ETH/USDT 5-minute closes from the Binance public market API, 29 October 2026, 18:00 UTC through the latest closed bar when the file was saved. The dashed line is 20:24 UTC, labeled outflow reports. Dollar prints in the prose are the X posts cited above, not these closes.
The line is already off its 18:00 area before the 20:24 mark, and the steeper step comes after the mark. That timing does not prove the wallet debit caused the earlier step. It does not prove the later step was the 167,464.25 ETH hitting a bid. The chart is the exchange's closes. The posts are what the accounts wrote. They are filed side by side.
In listed markets a custodian's debit advice and the exchange's last sale are different documents. A prime broker does not take the debit advice as the print, and does not take the print as proof of which book sold. Thursday's Ether tape is that split. The debit advice is the Etherscan transfer of 167,464.25 ETH at 20:24:23 UTC, warning included. The prints are the posts: $2,335 to $2,255 at 20:51 UTC, and below $2,250 at 20:55 UTC, with a chart header on the second post that does not match its text.
The check that fails is treating every large number in the hour as the Ether move. About $2.53 billion, about $2.77 billion, about $2.8 billion, $971 million, more than 1.567 billion, and about $823 million are all figures from posts above. None of them is the $2,335 to $2,255 line. A risk system that takes the largest number in the thread and labels it as Ether will mis-state both the coin and the size.
The prior day's $21.41 million ETF outflow belongs in a third folder. It is a fund-share print. Putting it on the Thursday night wallet transfer would make a small, dated flow look like part of 167,464.25 ETH. It is not.
This is the operational file. It adds no price beyond the prints already cited.
Reports said 167,464.25 ETH left the wallet labeled Binance 14. The amount is the Etherscan transfer on the hash Tree News posted, at 20:24:23 UTC, not a back-solve from the spot drop. The page tags the destination Binance Hot Wallet Exploiter 2 and also shows the revert warning quoted above. What that destination did with the ether after the transaction is not in the posts opened here, so it is not stated.
The freeze file is split. Three posts from 21:05 to 21:15 UTC say about $971 million of USDT. CZ adds about $823 million at Circle. Tree News at 21:26 UTC posts more than 1.567 billion USDT, attributed to Ardoino through Bloomberg. A desk has a set of claims, not one frozen balance, until the issuers reconcile them. None of those claims is an Ether quote.
The exchange file is split the same way. CZ: it looks like a hack, user funds are safe, he expects full coverage, and he does not run Binance.com. Binance at 21:29 UTC: potential security issue, investigating, user funds are completely safe. The 21:20 screenshot: impact not confirmed, plus a scam warning. Only the exchange can close that gap. This article does not.
No. Nebraskangooner at 20:51 UTC printed $2,335 to $2,255. The Kobeissi Letter at 20:55 UTC said Ether fell below $2,250. The chart on that post shows a last near $2,261.39 and a header change of 0.07 percent. Those are three figures from two posts. This article does not average them.
No. The 167,464.25 ETH figure is the transfer on the Etherscan page for the hash Tree News posted, at 20:24:23 UTC, from Binance 14. The spot figures are later posts about the market. A wallet debit is not a trade confirmation. Nothing opened here shows a sale, or rules a sale out.
Book the posts, not a blend. Tree News at 21:05 UTC, The Kobeissi Letter at 21:14 UTC, and CZ at 21:15 UTC use about $971 million for Tether. Tree News at 21:26 UTC posts a Bloomberg attribution of more than 1.567 billion USDT. CZ, not the Binance account, is the source here for about $823 million at Circle.
Not in the account post opened here. At 21:29 UTC the Binance account said it was investigating a potential security issue and that user funds are completely safe. CZ, at 21:15 UTC, said it does look like a hack. A screenshot in a 21:20 UTC Kobeissi post uses different wording. The gap is the record.
No. The posts and the Etherscan page are what had already been written and what the transaction page showed. The chart is closes that had already closed. There is no target in this article, and no path past that window.
This article records the move that already happened. It is not a price prediction.
This is not financial advice.
