Published
/
Updated
Tables and diagrams are easier to read on a larger screen.
The Binance Hot Wallet Drain / Notes
Investigation Notes 3 / Notes
How this report
was built
Seven editions in six days. This page keeps the correction history, the withdrawn totals and the audit trail, so the report itself can stay clean.
The method
Every claim is registered when it is made. Every figure points at a hash, a block or a named statement.
01
Claim register
155 claims, one per line, with a status and an evidence reference. A correction chains a new claim; it never overwrites the old one.
02
Evidence register
93 rows held internally. Each records the chain, block, raw amount, decimals, source, retrieval time, confidence and limitation. The evidence page publishes what a reader needs to check a finding.
03
Fixed cutoffs
Every chain is pinned to a block or tip. Event time, data cutoff, retrieval time and release time are kept separate.
Version history
Every edition that survives is linked below with its checksum. R2 was replaced in place by R2.2, so no separate R2 file exists.
Investigation NotesNotes 1 to R6, in order
N1
30 October 2026, 13:06 UTC
First snapshot
The sweep, the ten chains, the holding wallets, the initial freezes. Nine pages.
SupersededOpen the PDFR2
31 October 2026, 09:19 UTC
Optimism, AVAX and the blocklist
The 44.23M OP move, the AVAX to ETH conversion, the blocklist cross-check. Eleven pages.
Replaced in placeNO SEPARATE FILER2.2
31 October 2026, 11:00 UTC
Metadata and timing
Metadata, timing and window corrections from an external review. Eleven pages.
SupersededOpen the PDFR3
31 October 2026, 12:45 UTC
Authorization and reconciliation
The OP authorization chain, the EIP-7702 rehearsal, the reconciliation, the appendix. Seventeen pages.
SupersededOpen the PDFR4
31 October 2026, built 13:56:44, first served 14:00:59
The Tron receipt-token route
A complete JustLend route from deposit to convergence, the pre-incident pipeline finding, publication corrections. Nineteen pages.
SupersededOpen the PDFR5
1 November 2026, data cut 09:10 UTC, first served 11:53 UTC
The four-swap correction
Four Chainflip swaps, the pass-through to an FBI-listed terminal, the TRX funding tree, and sixteen corrections. Twelve pages.
SupersededOpen the PDFR6
4 November 2026, fixed cutoffs 1 November, prepared 04:50 UTC
The intrusion and the scoreboard
Binance's root-cause account, the post-cutoff laundering status, the corrected TG5iB provenance, and a measured-versus-claimed scoreboard. Fourteen pages.
CurrentOpen the PDFRevision 4 was the strongest edition where it measured a hash, a block or a balance. It failed where it turned those measurements into a total. Revision 5 keeps the measurements and removes the totals that do not partition. Revision 6 adds the company's root-cause account and a scoreboard, and corrects the cover's TG5iB provenance. The fixed chain cutoffs stay at 1 November; the principal positions were re-checked on 4 November.
| Edition | File | Bytes | SHA-256 |
|---|---|---|---|
| N1 | investigation-notes-1.pdf | 622,586 | f88a0af0d55855f0c6ace68812743fc38d827d41e9fd4db2cd5b44cdf32bd755 |
| R2.2 | investigation-notes-2.pdf | 936,377 | 62460fee10acd75f727a8a5428c0bffb224d27c03e68ebdf37a739f6c8ba7c78 |
| R3 | investigation-notes-3.pdf | 796,634 | f947d38c1d308292d2f938d17839392e409dd93ac74281a8b827cfb5ffedbc9a |
| R4 | investigation-notes-4.pdf | 850,743 | 0bc0306ba384749ce54e339ac2034edd3f714e52489cfc9abd9828b49e384d6c |
| R5 | investigation-notes-5.pdf | 769,341 | 9a6c5bb6cc6b196c0d68277e07664c0bc0339f96f6880b7e649985779503398a |
| R6 | investigation-notes-6.pdf | 851,127 | bc8ef4e641f34b1f0a1da8b2b6e1c86ce5554b3785b038f2948bfadb68caebe9 |
The twenty-two corrections
What the earlier editions said, what replaced it, and how the replacement is classified.
| ID | Earlier statement | Replacement | Status |
|---|---|---|---|
| C01 | Rows presented as a partition. 3.729B against a 3.051B subtotal. | The rows are not a partition. The 678.2M difference is an arithmetic consequence of mixed scopes. | Contradicted |
| C02 | Frozen bridge 2.6946B. | A candidate bridge, not a deduplicated total. Arithmetic verified, classification open. | Candidate |
| C03 | Valuing 481,581 ETH as stolen overstates the theft two to three times. | 170,426.16 is the Binance-14 native component. The denominator is a mixed balance. Not a theft ratio. | Withdrawn |
| C04 | Arbitrum L1 trigger not found. Action dated 31 October. | L1 is public: block 26,301,886, 30 October 00:08:35 UTC. The L2 execution is block 519,514,685. | Corrected |
| C05 | Binance 14 signs its own revocation at 00:10:35. | Inclusion is not signing time. The signer and signing environment are not established. | Wording |
| C06 | The 50-tuple batch proves the operator could not read the nonce. | 15 tuples were above the nonce, 34 below. After the sweep the nonce passed every tuple. Inference withdrawn. | Withdrawn |
| C07 | The 1,000 USDT leg returned to a market maker. The difference is a protocol fee. | The 573,892.358889 USDT was bought from a public AMM pool. No fee event is in the receipts. Mechanism not proved. | Corrected |
| C08 | A 52-edge pre-incident Tron pipeline. | Publish the dataset or withdraw the count. Pre-incident use does not discriminate a service from one actor. | Unresolved |
| C09 | 64 approval records, twenty orders of magnitude inflated. | One Approval is confirmed by the raw receipt. The 64 count is withdrawn; a full re-pull was not completed. | Withdrawn |
| C10 | Tron intervals of 41 seconds. | The intervals are 45 and 39 seconds. Historical guardian and timelock claims need the exact block state. | Corrected |
| C11 | Fifteen embedded links, no usable transaction index. | Full hashes stay in the text and every critical row carries its hash. Ten of them are listed in full on the evidence page. | Corrected |
| C12 | Executor treated as a Safe signer. Separate multisigs as separate organisations. | An executor or submitter is not necessarily a signer. Separate contracts do not establish separate people. | Wording |
| C13 | A single BTC change figure of 0.00089173. | Of the receipts, 0.00063719 is dust-pattern output, 0.00046563 is change and 0.00001000 is new dust. The label was wrong for 42,610 sats. | Corrected |
| C14 | Eighteen hours of rehearsal. A 22:55 start. | Preparation is about 17h52m from the 02:28:59 sweeper deployment. The 16:47 and 22:55 endpoints are withdrawn. | Corrected |
| C15 | R3 cover, footer and social labels. A 14:30 publication time. | R5 metadata, footer and social image. R4 was built 13:56:44 and first served 14:00:59. | Corrected |
| C16 | Ten-chain scope presented as the total. | TRM ten chains, Elliptic eleven in its laundering footprint, Bitquery nine. Keep the scopes separate. | Vendor |
| C17 | The cover said the TRX traced back to TG5iB and called it the hub. | TG5iB is a direct branch. The hub took 638,190,941.68 TRX from TPBk and 9,986.91 from TCzBT. TPBk's own TRX inflows on 29 October total 11,009.000025, so its balance source is open. | Corrected |
| C18 | PDF retained 'Optimism alias' on the cover, the money-flow page and the address table. | Every occurrence now reads 'receiving address'. | Corrected |
| C19 | XRP, SOL and THORChain were described as parked and halted after they moved. | XRP moved to six addresses on 2 November; about 87,000 SOL moved by 3 November; THORChain was down to 3 of 13 halted chains on 4 November. | Corrected |
| C20 | Replenishment was stated as 95%. | The 2 and 3 November updates say 95%; the 3 November blog says 98% as of 31 October. Both are attributed and the gap is not resolved. | Disputed |
| C21 | The report had no root-cause section and treated the signing route as wholly unknown. | Binance's 3 November account is added as company evidence: four stages, one signing service. It does not name the signer or publish the MPC audit trail. | Added |
| C22 | Aave Slope2 was described as unexecuted without a 4 November re-read. | A 4 November read shows 10.00 / 10.00 / 35.00 / 50.00%. The restoration executed after the cut; a restored curve is not a return. | Corrected |
The four-swap discovery
The Tron route was described as three swaps for two editions. It is four.
WHAT WAS MISSED
A fourth deposit channel
Channel 15475340-Tron-21305 was funded at 13:34:39 with 34,357 USDT and paid 15.418418499089104654 ETH at 13:38:23. It paid out at 13:38:23, nine minutes before the first Vault collection in the record. A table built from the Vault collections could not see it.
HOW IT WAS FOUND
The payouts did not sum
The three known payouts total 256.636981051403916926 ETH. The common recipient 0xc6ca6f2f received 272.055399550493021580 ETH. The 15.418418499089104654 ETH difference is the fourth swap, and its deposit hash was already in the evidence register.
WHAT IT CHANGES
A route, not a return
Four deposits from four Tron channels all settle to the same Ethereum address. That address is a pass-through, not a stopping point. Twenty-four seconds later the balance moves to a fresh EOA that is on the FBI list.
The FBI-listed terminal
The address that holds the ETH is a fresh account with no outbound.
0x5915F563399b5d2C3A42A08F77E290Ae8121B260. Nonce 0, code 0x, balance 272.055383921583158580 ETH. It received the full pass-through at 14:03:59 and has no outbound. The FBI advisory lists it. A list is a label, not a freeze, and the funds are not returned.
The outbound plus gas equals the four payouts
Why the pass-through is the same money, not a similar amount. Full precision below.
Payouts
272.055399550493021580
Pass-through
272.055383921583158580
Gas is 0.000015628909863 ETH, which is 0.0000057% of the payouts. At any bar width that a page can show it is invisible, so it is stated as an equation rather than drawn: 21,000 gas at 744,233,803 wei. 272.055383921583158580 + 0.000015628909863 = 272.055399550493021580 ETH.
272.055383921583158580 + 0.000015628909863 = 272.055399550493021580 ETH
The TRX funding branches
The TRX that bought the USDT did not come from a market maker.
Direct branchTG5iB46,383,069.13 TRX to the hub
→
Conversion hubTRBdW684,583,971.13 TRX in, two branches before the swap
→
IntermediateTM32ED4.426M TRX through two funders
→
TerminalTAf3878 seconds old at the swap
Why this matters. The Chainflip route and the TNhpf flow share the TRBdW hub. Two branches had fed it before the swap: 46,383,069.13 TRX directly from TG5iB and 120,000,000 TRX from the first of five fan-out wallets. Four more fan-out wallets delivered 518,200,902 TRX on 31 October, after the swap. That is a common funding hub, not proof of one controller or of exclusive provenance.
What we got wrong, and how it was caught
CAUGHT BY ARITHMETIC
The 3.729B total
Three priced rows summed to more than the stablecoin subtotal the same report published. The excess was not overlap. It was the cost of adding rows with different scopes.
CAUGHT BY RE-READING THE RECEIPT
The 64 approval records
One Approval event exists, with no Transfer. The general feed-classification defect is plausible. The count itself was never re-established, so it was withdrawn.
CAUGHT BY CHECKING THE COUNTERPARTY
The market maker that was a pool
The TRX call paid a UniversalRouter, which paid a V3-style pool. The pool sent USDT back. It was never a market maker returning its own funds.
CAUGHT BY READING THE OTHER CHAIN
The Arbitrum trigger that was public
The L1 authorization was on Ethereum all along, ten minutes before the L2 execution. The earlier search looked only at Arbitrum.
Evidence
What the report rests on
The fixed cutoffs, ten rows that carry the case, all nineteen Bitcoin outpoints, the four Chainflip legs, the source register and every address in full. Check any row on a public explorer