Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.

All briefings

Briefing for 2026-11-01

Generated . Each line is a statement somebody made, not a finding of this site.

  1. Reportedclaim Binance stated that it will absorb the financial impact of the stolen funds rather than its users.

    BBC News. Original

  2. Reportedclaim Binance stated that withdrawals had been restored on several of its networks after being suspended following the hack.

    BBC News. Original

  3. Reportedclaim The FBI stated that North Korea was responsible for the attack.

    BBC News. Original

  4. Reportedclaim The FBI stated that it observed hackers converting stolen assets into Ethereum and expected further conversion using decentralised finance and instant swap services.

    BBC News. Original

  5. Reportedclaim Binance stated that it had replenished the stolen assets using various funds and its own corporate treasury.

    BBC News. Original

  6. Reportedclaim Binance stated that all holdings of bitcoin, Ethereum, and Tether, along with seven other widely-traded crypto assets, are covered.

    BBC News. Original

  7. Reportedclaim Binance's initial investigation suggested an engineer's laptop was compromised, allowing access to unauthorised withdrawals, but a later update said they had uncovered additional points of breach.

    BBC News. Original

  8. Reportedclaim Richard Teng, Binance's co-chief executive officer, stated that the hack was carried out by more than one person using sophisticated methods to hide their tracks.

    BBC News. Original

  9. Reportedclaim Binance stated that it had frozen around $3bn of stolen assets after working with law enforcement, intelligence firms, and partners.

    BBC News. Original

  10. Reportedclaim The US Secret Service stated that it is working around the clock with private sector partners to identify, freeze, trace, and recover funds stolen from Binance.

    BBC News. Original

  11. Reportedclaim Binance stated that it has set aside more than $6.34bn in company funds to cover the losses.

    BBC News. Original

  12. Reportedclaim Hacken said that estimates of the loss from the hack range from about $6.3B to $6.43B, making it the largest crypto theft on record.

    Hacken. Original

  13. Reportedclaim Hacken reports that between $2.7B and $2.84B was frozen within hours of the attack, mostly stablecoins.

    Hacken. Original

  14. Reportedclaim Binance stated it will cover all losses from its SAFU reserve and company funds, and that user funds are safe.

    Hacken. Original

  15. Reportedclaim Three analytics firms linked the attack to North Korean state actors.

    Hacken. Original

  16. Reportedclaim Hacken said that the first transfers occurred at 20:05 UTC on the XRP Ledger, where five Binance wallets sent 233 million XRP to a single address.

    Hacken. Original

  17. Reportedclaim Hacken said that at 20:20 UTC, a Bitcoin hot wallet sent out 18,270 BTC.

    Hacken. Original

  18. Reportedclaim Hacken said that at 20:24 UTC, one transaction moved about $2.53B out of a single Ethereum wallet.

    Hacken. Original

  19. Reportedclaim Hacken said that Tether froze 971.1M USDT at 21:01 UTC, 37 minutes after the Ethereum transaction.

    Hacken. Original

  20. Reportedclaim Hacken said that Circle froze 823M USDC at 21:04 UTC.

    Hacken. Original

  21. Reportedclaim Hacken said that Binance stated the verified frozen total was $2.54B at 23:35 UTC.

    Hacken. Original

  22. Reportedclaim Hacken said that the Arbitrum Security Council moved 8,426 ETH and 74.6M ARB out of the attacker's reach at 00:08 UTC on October 30.

    Hacken. Original

  23. Reportedclaim Hacken said that the verified frozen total reached $2.84B, which is 44% of the theft, at 08:00 UTC.

    Hacken. Original

  24. Reportedclaim Binance's update of 02:23 UTC on October 30 stated that its initial investigation suggests the incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions.

    Hacken. Original

  25. Reportedclaim Binance co-CEO Richard Teng said the attacker did not simply use one engineer's permissions and that it was not a single 'one-click' action.

    Hacken. Original

  26. Reportedclaim Hacken said Ripple and World Liberty Financial froze their tokens inside the compromised wallet, which stopped new deposits of those tokens from being taken.

    Hacken. Original

  27. Reportedclaim Hacken reports that two analytics firms attribute the theft to TraderTraitor, a North Korean hacking unit, and a third firm calls it likely.

    Hacken. Original

  28. Reportedclaim Hacken notes that stolen Binance funds were seen mixing in real time with funds from the Bitget theft, which had been attributed to North Korean actors, and that funds from both thefts reached the same Ethereum address as first reported by ZachXBT.

    Hacken. Original

  29. Reportedclaim Hacken said that the overlap with Bitget is small, with about $39,000 of Binance funds at the shared address against about $510,000 from Bitget, and that the thief left most of the stolen USDT unconverted for 37 minutes on Ethereum and 46 on Tron.

    Hacken. Original

  30. Reportedclaim Teng said the investigation has not attributed responsibility to any individual, and Binance says it is working with law enforcement to confirm who is behind it.

    Hacken. Original

  31. Reportedclaim Binance reported that approximately $6.3 billion was impacted in an apparent hack.

    npr.org. Original

  32. Reportedclaim Binance stated that it worked with blockchain partners to freeze roughly $3 billion in affected assets.

    npr.org. Original

  33. Reportedclaim Binance announced that it was beginning to recover assets for users on Friday.

    npr.org. Original

  34. Reportedclaim Binance stated that withdrawals have been suspended and are expected to resume in the next day or two.

    npr.org. Original

  35. Reportedclaim Binance stated that it will cover all losses.

    npr.org. Original

  36. Reportedclaim Binance stated that an initial investigation suggested the incident may have involved a compromised laptop, but a subsequent investigation uncovered additional points of breach.

    npr.org. Original

  37. Reportedclaim TRM attributed the attack to TraderTraitor, which it described as North Korea's elite hacking unit, with high confidence.

    npr.org. Original

  38. Reportedclaim TRM stated that an attacker moved approximately USD 6.36 billion out of Binance wallets on ten blockchains, most of it in about 20 minutes.

    npr.org. Original

  39. Reportedclaim TRM stated that the hack would make it the largest cryptocurrency theft on record.

    npr.org. Original

  40. Reportedclaim TRM stated that several features of the attack match earlier North Korea-linked heists, including the Bybit hack.

    npr.org. Original

  41. Reportedclaim Jonathan Levin, co-founder and CEO of Chainalysis, wrote that the Binance hack was likely done by DPRK group TraderTraitor.

    npr.org. Original

  42. Reportedclaim A Binance spokesperson said the company is working closely with law enforcement partners to confirm the identity of the criminals and bring them to justice.

    npr.org. Original

  43. Reportedclaim Changpeng Zhao posted that user funds are safe, but added that the theft does look like a hack on Binance.

    npr.org. Original

  44. Reportedclaim NPR reported Changpeng Zhao saying that he does not manage Binance anymore but, as a shareholder, expects all user funds will be fully covered.

    npr.org. Original

  45. Theoryclaim NPR quoted Kok Tin Gan, cofounder and CEO of NyxLab, as saying this looks like one signature that gave the attacker a never-expiring, full-access token to a Binance hot wallet.

    npr.org. Original

  46. Reportedclaim Elliptic's analysis states that $6.43 billion in cryptoassets was stolen from Binance on October 29, 2026.

    Elliptic. Original

  47. Reportedclaim Binance initially linked the breach to a compromised DevOps engineer's laptop but later stated it uncovered additional points of breach in a complex attack not carried out by one person.

    Elliptic. Original

  48. Reportedclaim Elliptic has verified $2.85 billion of frozen or seized funds, which is 44% of the theft, mostly USDT and USDC.

    Elliptic. Original

  49. Reportedclaim Binance announced it has begun reopening withdrawals, starting with the Bitcoin network.

    Elliptic. Original

  50. Reportedclaim Binance stated it will cover all losses using its SAFU fund and company funds, having reserved more than $6.34 billion of company funds.

    Elliptic. Original

  51. Reportedclaim Binance co-CEO Richard Teng said he was hopeful that withdrawals would resume before Sunday, October 31.

    Elliptic. Original

  52. Reportedclaim The FBI attributed the theft to TraderTraitor, a North Korean state-sponsored hacking group, on October 31.

    Elliptic. Original

  53. Reportedclaim Blockaid said that at Binance's estimate, the theft was $6.3B, making it the largest on record and more than four times the $1.5B taken from Bybit in February 2025.

    blockaid.io. Original

  54. Reportedclaim Blockaid said that eleven Binance hot-wallet keys signed transfers to an address created minutes earlier, and one signed an EIP-7702 authorization.

    blockaid.io. Original

  55. Reportedclaim Blockaid said that about $3B was frozen within hours, while most of the ETH and other native assets stayed with the attacker.

    blockaid.io. Original

  56. Reportedclaim Elliptic said the stolen USDT reached the attacker's main Ethereum wallet at 20:24 UTC, that Tether froze that wallet 37 minutes later locking 1.18 billion USDT, and that Circle froze the 823 million USDC in the same wallet three minutes after that.

    Elliptic. Original

  57. Reportedclaim Elliptic said the Arbitrum Security Council took emergency action to move assets out of the attacker's reach, and that Optimism's governance appears to have done the same on October 31, moving 44 million OP (around $5 million).

    Elliptic. Original

  58. Reportedclaim Elliptic said stablecoins make up 94% of the frozen funds, almost entirely on Ethereum and Tron, and that nothing stolen on Bitcoin, the XRP Ledger, Solana or NEAR has been frozen.

    Elliptic. Original

  59. Reportedclaim Elliptic said the attacker converted around $786 million of stablecoins into ETH and TRX before the freezes landed.

    Elliptic. Original

  60. Reportedclaim Elliptic said 434 million USDT was swapped for 160,451 ETH on Ethereum at a loss of 12% to 26% against the market price, which it read as the attacker prioritising speed over value.

    Elliptic. Original

  61. Reportedclaim Elliptic said a second attacker wallet deposited 59.9 million USDT into Aave as collateral and borrowed 19,762 ETH before Aave froze the affected markets.

    Elliptic. Original

  62. Reportedclaim Elliptic said 234 million USDT was swapped for 638 million TRX on SunSwap on Tron, and 48 million RLUSD was sold on Ethereum before Ripple froze the remainder.

    Elliptic. Original

  63. Reportedclaim Elliptic said the 18,270 BTC was split through a peel chain into 19 addresses, most holding 1,000 BTC each, and that none of it had yet been sent to a service.

    Elliptic. Original

  64. Reportedclaim Elliptic said that on October 30 the attacker sold all stolen AVAX for USDC between 11:38 and 12:29 UTC, bridged it to Ethereum using Circle's CCTP, and swapped it for 7,242.8 ETH.

    Elliptic. Original

  65. Reportedclaim Elliptic said the attacker controls around $3.25 billion of assets that an issuer cannot freeze, spread across more than 800 addresses, including around 584,000 ETH, 18,327 BTC and 233 million XRP.

    Elliptic. Original

  66. Reportedclaim Blockaid said that about $6.3B was stolen from Binance's hot wallets on October 29, 2026, by Binance's own estimate, and described it as the largest crypto theft on record.

    blockaid.io. Original

  67. Reportedclaim Blockaid said Tether and Circle froze about $1.8B in the main collection address within 40 minutes, and that with later freezes by other issuers and the Arbitrum Security Council, Binance puts the verified total frozen at about $3B.

    blockaid.io. Original

  68. Reportedclaim Blockaid said the attacker first drained a Binance wallet it calls Binance 14 starting 20:24 UTC in a single transaction worth about $2.5B, minutes after Binance's own signing infrastructure, which it said was under the attacker's control, signed an EIP-7702 authorization delegating it to an attacker-deployed sweeper.

    blockaid.io. Original

  69. Reportedclaim Blockaid said the operator address 0x7C8601d4645b93cea45F71e118A729332e6B5CA0 was funded through three Tornado Cash withdrawals starting October 28.

    blockaid.io. Original

  70. Reportedclaim Blockaid said that at 20:20:59 UTC on October 29 the operator sent a transaction to the wallet it calls Binance 14 carrying 50 EIP-7702 authorizations signed with that wallet's key, each delegating the wallet to the sweeper.

    blockaid.io. Original

  71. Reportedclaim Blockaid said that at 20:24:23 UTC on October 29 the operator called sweep on Binance 14, sending 167,464 ETH, 1.615B USDT and about 60 other tokens to a collection address with no prior history, a basket it valued at about $2.5B.

    blockaid.io. Original

  72. Reportedclaim Blockaid said that at 20:41:23 UTC the operator used the still-delegated Binance 14 to move 780M USDC from a Circle smart account to the collection address, followed by another 43M USDC.

    blockaid.io. Original

  73. Reportedclaim Blockaid said that at 21:44 UTC the operator swept Binance 14 again for 200M USDT and 13 other tokens deposited since the first sweep.

    blockaid.io. Original

  74. Reportedclaim Hacken said the chain confirms Binance 14 signed a new authorization at 00:10:35 UTC on 30 October that reset its delegation, 3 hours 46 minutes after the sweep.

    Hacken. Original

  75. Reportedclaim Cointelegraph reported that a Binance spokesperson said on Thursday that the exchange was investigating reports of a potential security issue and had not confirmed any impact on user funds.

    Cointelegraph. Original

  76. Reportedclaim Cointelegraph reported that blockchain researcher Spreek first raised concerns, posting on X that assets from a Binance-linked Ethereum wallet had been moved to a newly created address through a contract call allegedly funded by Tornado Cash.

    Cointelegraph. Original

  77. Reportedclaim Cointelegraph reported that Arkham Intelligence identified wallets labeled binance-hacker-1029 holding approximately $5.84 billion, and noted that this is the wallets' reported holdings, not a confirmed estimate of stolen funds.

    Cointelegraph. Original

  78. Reportedclaim Cointelegraph reported that Changpeng Zhao said the activity appeared to be a hack and that Tether and Circle had frozen approximately $971 million and $823 million respectively.

    Cointelegraph. Original

  79. Reportedclaim Cointelegraph reported that Circle CEO Jeremy Allaire said Circle had frozen more than $800 million in USDC in coordination with law enforcement.

    Cointelegraph. Original

  80. Reportedclaim Cointelegraph reported that Tether CEO Paolo Ardoino said Tether had frozen more than $1.567 billion in USDT linked to the potential exploit.

    Cointelegraph. Original

  81. Reportedclaim Cointelegraph reported that Blockaid said it had identified roughly $3.3 billion in suspicious transfers involving Binance-linked wallets across Ethereum, Arbitrum and Avalanche.

    Cointelegraph. Original

  82. Reportedclaim Cointelegraph reported that Aave froze markets across its V3 and V4 deployments as a precaution following the Binance hack.

    Cointelegraph. Original

  83. Reportedclaim Cointelegraph reported that, according to Yi He, World Liberty Financial froze $27 million in USD1 and $2 million of WLFI, and that World Liberty Financial co-founder and CEO Zach Witkoff said USD1 had frozen the $27 million associated with the hack.

    Cointelegraph. Original

  84. Reportedclaim Cointelegraph reported that Binance said the verified total of assets frozen had reached $2.54 billion, and that Binance said this clarified differing figures in circulation, including references to $1.8 billion.

    Cointelegraph. Original

  85. Reportedclaim Cointelegraph reported that, according to Ripple's Jack McDonald, Ripple was freezing RLUSD linked to the Binance hack and coordinating with relevant parties, without disclosing an amount.

    Cointelegraph. Original

  86. Reportedclaim Cointelegraph reported that Binance said it had temporarily suspended deposits while it conducts security checks, freezes funds and coordinates with law enforcement.

    Cointelegraph. Original

  87. Reportedclaim Cointelegraph reported that Chainalysis said its current estimate of the amount stolen from Binance is $5.912 billion at the time of theft.

    Cointelegraph. Original

  88. Reportedclaim Cointelegraph reported that Binance said the current verified amount of assets frozen from the hack was $3 billion.

    Cointelegraph. Original

  89. Reportedclaim Cointelegraph reported that the Arbitrum Security Council said it executed a transaction to freeze $30.5 million, involving 74.6 million ARB and 8,425 ETH, and that the funds were transferred to an intermediary frozen wallet.

    Cointelegraph. Original

  90. Reportedclaim Cointelegraph reported that Binance said withdrawals remained paused while it completes a security revamp, with service expected to resume within 48 hours.

    Cointelegraph. Original

  91. Reportedclaim Cointelegraph reported that Chainalysis CEO Jonathan Levin said the hack was likely carried out by TraderTraitor and, in a post on X, put the theft at $6.4 billion.

    Cointelegraph. Original

  92. Reportedclaim Cointelegraph reported that onchain investigator ZachXBT said stolen funds from the Binance attack and the earlier Bitget exploit were commingled in the same address after arriving via THORChain.

    Cointelegraph. Original

  93. Reportedclaim Cointelegraph reported that Binance said its investigation had uncovered additional points of breach after initially pointing to a possibly compromised laptop, and that it remained on track to resume withdrawals in 45 hours.

    Cointelegraph. Original

  94. Reportedclaim Cointelegraph reported that Chainalysis said its investigators were observing never-seen-before laundering patterns with the stolen funds.

    Cointelegraph. Original

  95. Reportedclaim Cointelegraph reported that Binance said it had set aside more than $6.34 billion in company funds to cover losses, of which $5 billion was already held in the same tokens affected by the attack.

    Cointelegraph. Original

  96. Reportedclaim Cointelegraph reported that co-CEO Yi He said Binance was buying altcoins in quantities matching those stolen as it prepares updated proof of reserves.

    Cointelegraph. Original

  97. Reportedclaim Cointelegraph reported that a Binance spokesperson said the $5 billion in matching tokens is held in the exchange's custody and declined to disclose wallet addresses.

    Cointelegraph. Original

  98. Reportedclaim Cointelegraph reported that co-CEO Richard Teng said the attacker used an EIP-7702 delegation to gain execution authority over a hot wallet, and that the delegation did not pass through Binance's normal approval controls.

    Cointelegraph. Original

  99. Reportedclaim Cointelegraph reported that co-CEO Richard Teng said Binance was aiming to resume withdrawals within 40 hours and publish a full proof-of-reserves report by Monday.

    Cointelegraph. Original

  100. Reportedclaim TRM said an attacker moved approximately USD 6.36 billion out of Binance wallets on ten blockchains on October 29, 2026, most of it in about 20 minutes starting at 20:05 UTC.

    TRM Labs. Original

  101. Reportedclaim TRM said that valuing each transfer at the price when it was taken gives about USD 6.36 billion, and that at current prices the same assets are worth about USD 6.23 billion.

    TRM Labs. Original

  102. Reportedclaim TRM said Tether, Circle, Ripple and World Liberty Financial froze about USD 2.67 billion in stablecoins and Arbitrum's Security Council froze 8,426 ETH and 74.6 million ARB, a total of roughly USD 2.7 billion.

    TRM Labs. Original

  103. Reportedclaim TRM said that between 20:05 and 20:09 UTC five Binance wallets on the XRP Ledger sent 233.46 million XRP to a single attacker address.

    TRM Labs. Original

  104. Reportedclaim TRM said a Binance Bitcoin hot wallet sent 18,270 BTC to an attacker address at 20:20 UTC, and that the funds began splitting into round pieces inside the same block.

    TRM Labs. Original

  105. Reportedclaim TRM said the operator submitted a single Ethereum transaction at 20:20 UTC containing 50 authorizations signed by a Binance hot wallet, each pointing to a sweeper contract.

    TRM Labs. Original

  106. Reportedclaim TRM said that three minutes and 24 seconds after the delegation the operator instructed the Binance hot wallet to send its entire balance to an attacker-controlled address, moving 167,464 ETH and 63 tokens including 1.615 billion USDT in one transaction.

    TRM Labs. Original

  107. Reportedclaim TRM said Tether froze 971.1 million USDT in the main receiving wallet at 21:01 UTC, 37 minutes after the main sweep, and that later sweeps landed in that frozen wallet, which then held 1.175 billion USDT.

    TRM Labs. Original

  108. Reportedclaim TRM said Circle froze the 823 million USDC in the main receiving wallet at 21:04 UTC, in coordination with law enforcement.

    TRM Labs. Original

  109. Reportedclaim TRM said Ripple froze the wallet holding the stolen RLUSD at 22:01 UTC, with 40.5 million of the 88.5 million RLUSD still inside.

    TRM Labs. Original

  110. Reportedclaim TRM said World Liberty Financial froze the 27.8 million USD1 in the main receiving wallet at 22:10 UTC, and froze USD1 in the compromised Binance hot wallet at 22:26 UTC.

    TRM Labs. Original

  111. Reportedclaim TRM said Binance stated at 23:35 UTC that the verified total frozen had reached USD 2.54 billion.

    TRM Labs. Original

  112. Reportedclaim TRM said the Arbitrum Security Council used its emergency powers at 00:08 UTC to force two transfers out of the attacker's wallet on Arbitrum, moving 8,426 ETH and 74.6 million ARB, about USD 30 million, out of the attacker's reach.

    TRM Labs. Original

  113. Reportedclaim TRM said a second wave around 23:05 UTC reached Binance wallets on Avalanche and Polygon.

    TRM Labs. Original

  114. Reportedclaim TRM said that in its assessment the most likely explanation is that the attacker gained the ability to make Binance's hot wallet signing system sign transactions of its choosing across chains.

    TRM Labs. Original

  115. Reportedclaim TRM said it attributes the attack to TraderTraitor, which it calls North Korea's premier hacking unit, based on on-chain and off-chain intelligence sources.

    TRM Labs. Original

  116. Reportedclaim TRM said the attacker now held more than 420,000 ETH and 18,270 BTC, about USD 2.4 billion in assets beyond any issuer's reach.

    TRM Labs. Original

  117. Reportedclaim Hacken said that another count dates the first freezes at 21:14.

    Hacken. Original

  118. Reportedclaim Hacken's timeline table lists Ripple freezing 40.5M RLUSD at 22:01 UTC, citing TRM.

    Hacken. Original

  119. Reportedclaim Hacken's timeline table lists World Liberty Financial freezing 27.8M USD1 at 22:10 UTC, citing TRM.

    Hacken. Original

  120. Reportedclaim Hacken's timeline table lists a second wave of transfers from Binance wallets on Avalanche and Polygon at 23:05 UTC.

    Hacken. Original

  121. Reportedclaim Hacken's timeline table lists the first public attribution to TraderTraitor at 04:30 UTC on October 30, citing The Next Web.

    Hacken. Original

  122. Reportedclaim Hacken said stablecoin issuers began freezing 56 minutes after the first transfer, that Tether acted first at 21:01 and Circle three minutes later, and that Binance suspended deposits and withdrawals that night and published a written update at 02:23 UTC.

    Hacken. Original

  123. Reportedclaim Yahoo Finance reported that Tether said it froze nearly $1.57 billion in assets linked to the incident, while Circle froze more than $800 million.

    Yahoo Finance. Original

  124. Reportedclaim WIRED quoted Elliptic's Tom Robinson as saying that around $2.8 billion, or around 44 percent of the total stolen, had been frozen so far, almost all of it stablecoins.

    WIRED. Original

  125. Officialclaim Binance said in its Security Incident Update dated 2026-10-30 that its initial investigation suggested the incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to access a service container and submit unauthorized withdrawal transactions, and that it had found no evidence of any wallet private key leak.

    Binance. Original

  126. Officialclaim Binance said in its Security Incident Update dated 2026-10-30 that the estimated total impact sits at around $6.3B.

    Binance. Original

  127. Officialclaim Binance said in its Security Incident Update dated 2026-10-30 that it had worked with blockchain partners to freeze affected assets, with about $3 billion frozen on-chain so far.

    Binance. Original

  128. Officialclaim Binance said in its Security Incident Update dated 2026-10-30 that it will cover all losses from the SAFU fund and the company's funds, and that user funds are safe.

    Binance. Original

  129. Officialclaim Binance said in its Security Incident Update dated 2026-10-30 that as an immediate precaution it had temporarily suspended withdrawals, revoked the affected address authorisation, and engaged law enforcement and blockchain intelligence partners.

    Binance. Original

  130. Officialclaim Binance added a note to its Security Incident Update dated 2026-10-30 saying the announcement was updated on 2026-10-30 to clarify that deposits remain unaffected.

    Binance. Original

  131. Officialclaim Binance said in its Security Incident Update #2 that at around 20:05 UTC on 2026-10-29 its hot wallets were compromised, resulting in a loss of approximately $6.3B USD worth of token assets.

    Binance. Original

  132. Officialclaim Binance said in its Security Incident Update #2 that Binance will absorb the financial impact of the stolen funds, not its users.

    Binance. Original

  133. Officialclaim Binance said in its Security Incident Update #2 that it had set aside more than $6.34B in company funds, with $5B held in the exact impacted token assets, which it said meant it had covered approximately 80% of the impacted amount.

    Binance. Original

  134. Officialclaim Binance said in its Security Incident Update #2 that it had worked with law enforcement, blockchain intelligence firms, asset issuers and industry partners to trace and freeze affected assets, and that approximately $3 billion had been frozen on-chain to date.

    Binance. Original

  135. Officialclaim Binance said in its Security Incident Update #2 that its subsequent investigation had uncovered additional points of breach beyond a possibly compromised laptop, and that it had found no evidence that wallet private keys were leaked.

    Binance. Original

  136. Officialclaim Binance said in its Security Incident Update #2 that its tech team targeted starting to resume withdrawals within approximately 34 hours, subject to security checks, on a phased approach.

    Binance. Original

  137. Officialclaim Binance said in its Security Incident Update #2 that it was buying the remaining 20% of the lost token assets, planned an initial Proof of Reserves snapshot in 12 hours, and expected the result by Monday 2026-11-02.

    Binance. Original

  138. Officialclaim Binance said in Recovery Update #3 that the amount of the hacked loss it had covered was now up to 90%, up from approximately 80% in the previous update.

    Binance. Original

  139. Officialclaim Binance said in Recovery Update #3 that BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are fully backed 100%.

    Binance. Original

  140. Officialclaim Binance said in Recovery Update #3 that the replenishment employed a partial deployment of its SAFU fund, a portion of its Futures insurance fund, and its own corporate treasury.

    Binance. Original

  141. Officialclaim Binance said in Recovery Update #3 that it had taken a new Proof of Reserve snapshot at 2026-10-31 00:00 UTC and had updated the PoR website.

    Binance. Original

  142. Officialclaim Binance said in Recovery Update #3 that the full zero-knowledge proof takes approximately 40 to 50 hours to generate and was estimated to be ready by Tuesday 2026-11-03 UTC.

    Binance. Original

  143. Officialclaim Binance said in Recovery Update #3 that it remained on track to reopen withdrawals on Sunday 2026-11-01.

    Binance. Original

  144. Officialclaim Binance said in Recovery Update #3 that it is committing to replenishing the SAFU fund to approximately US$1 billion.

    Binance. Original

  145. Officialclaim Binance said in Recovery Update #4 that it was preparing to resume phase one of withdrawals on 2026-11-01 between 06:00 and 09:00 UTC.

    Binance. Original

  146. Officialclaim Binance said in Recovery Update #4 that it had now covered approximately 95% of the impacted amount, up from 90% in the prior update, with the outstanding 5% in less liquid tokens outside the top ten.

    Binance. Original

  147. Officialclaim Binance said in Recovery Update #4 that it will publish a post-incident report with further details once the investigation is complete.

    Binance. Original

  148. Officialclaim Binance said in Recovery Update #4 that deposit services remain open and are not affected by the incident.

    Binance. Original

  149. Officialclaim The FBI said in an alert dated October 31, 2026 that North Korea was responsible for the theft of more than $6 billion in virtual assets from Binance on or about October 29, 2026, and that it refers to this North Korean activity as TraderTraitor.

    FBI. Original

  150. Officialclaim The FBI said in its alert that, together with the USSS and IRS-CI, it had observed TraderTraitor actors converting stolen assets primarily into Ethereum, and expected them to be laundered further through DeFi and instant swap services.

    FBI. Original

  151. Officialclaim The FBI said in its alert that it, the USSS and IRS-CI urge private sector entities to block transactions with or derived from the addresses TraderTraitor actors are using to launder the stolen assets.

    FBI. Original

  152. Officialclaim The FBI said in its alert that the addresses it lists (ETH, BTC and SOL) are holding or have held assets from the theft and are operated by or closely connected to North Korean TraderTraitor actors.

    FBI. Original

  153. Reportedclaim Chainalysis said funds began leaving Binance hot wallets around 4:20 p.m. ET on October 29, 2026, and that unauthorized transfers totaled approximately $6.4 billion.

    Chainalysis. Original

  154. Reportedclaim Chainalysis said it attributes the hack to TraderTraitor, a North Korean cybercrime group.

    Chainalysis. Original

  155. Reportedclaim Chainalysis said freezes started by 5:14 p.m. Eastern.

    Chainalysis. Original

  156. Reportedclaim Chainalysis said approximately $2.8 billion had been frozen so far.

    Chainalysis. Original

  157. Reportedclaim Chainalysis said it announced its attribution to TraderTraitor on October 30 at 12:30 a.m. Eastern Time.

    Chainalysis. Original

  158. Reportedclaim Chainalysis said the attacker swapped $325 million in stablecoins into $285 million in ETH over nearly 20 minutes to try to stay ahead of the freezes.

    Chainalysis. Original

  159. Reportedclaim Chainalysis said many addresses receive exactly 1 TRX, then additional funds, then forward the funds, which it said suggests a programmatic process.

    Chainalysis. Original

  160. Reportedclaim Elliptic said the main Tron distribution wallet had sent funds every hour for 31 hours straight, with a longest pause of 46 minutes and no overnight break.

    Elliptic. Original

  161. Reportedclaim Elliptic said swaps into THORChain use the same amounts repeatedly, with one value appearing 19 times, which it read as evidence of software-driven laundering.

    Elliptic. Original

  162. Reportedclaim Elliptic said that about $6.43 billion was stolen from Binance across 11 blockchains on October 29.

    Elliptic. Original

  163. Reportedclaim Elliptic said at 22:41 UTC on October 31 that about $196 million had been sent out of the main Tron distribution wallet to around 200 wallets.

    Elliptic. Original

  164. Reportedclaim Elliptic said it publishes a free CSV of every address its investigators have linked to the Binance hack.

    Elliptic. Original

  165. Reportedclaim BleepingComputer reported that Binance was investigating a potential security breach involving up to $5.8 billion in digital assets.

    BleepingComputer. Original

  166. Reportedclaim BleepingComputer reported that Arkham Intelligence's $5.78 billion figure is the value of assets held across all the wallets it tracked, not a confirmed amount stolen from Binance.

    BleepingComputer. Original

  167. Reportedclaim The Block reported that Binance said it had reserved over $6.34 billion in company funds to offset its losses.

    The Block. Original

  168. Reportedclaim The Block reported that co-CEO Yi He said Ripple "promptly" froze roughly $200 million in associated funds.

    The Block. Original

  169. Reportedclaim The Block reported that Chainalysis estimated roughly $5.9 billion was stolen at the time of the theft.

    The Block. Original

  170. Reportedclaim Decrypt reported that Chainalysis and TRM Labs put the total at around $6.4 billion, more than four times the previous record.

    Decrypt. Original

  171. Officialclaim Binance told users in its first 30 October update to rely only on official Binance channels for updates.

    Binance. Original

  172. Officialclaim Binance said in its first 30 October update that it was working with law enforcement partners to confirm the identity of the criminals.

    Binance. Original

  173. Officialclaim Binance said it would cover all stolen funds through its SAFU fund and its corporate treasury.

    Binance. Original

  174. Officialclaim Binance said in its second 30 October update that it expected to share further technical findings within about 48 hours.

    Binance. Original

  175. Officialclaim Binance said it would publish a detailed technical report on what happened and the safeguards being added.

    Binance. Original

  176. Officialclaim Binance told users in its second 30 October update to follow only its official channels or contact official Customer Support for verified updates.

    Binance. Original

  177. Reportedclaim Chainalysis said that this repeated sequence suggests a programmatic process for moving and redistributing the stolen funds.

    Chainalysis. Original

  178. Reportedclaim Chainalysis said its strongest evidence for TraderTraitor was seeing Binance funds commingle in real time with funds stolen in the Bitget exploit.

    Chainalysis. Original

  179. Reportedclaim Chainalysis said stablecoin issuers began freezing funds by 5:14 p.m. ET on 29 October.

    Chainalysis. Original

  180. Reportedclaim TRM Labs said preparation began at least 36 hours before the theft, with the operator wallet receiving three small Tornado Cash withdrawals from the morning of 28 October.

    TRM Labs. Original

  181. Reportedclaim TRM Labs attributed the attack to TraderTraitor, which it called North Korea's elite hacking unit, with high confidence.

    TRM Labs. Original

  182. Reportedclaim TRM Labs said early indicators suggested the attacker had phished the Ethereum authorizations, but that this leaves the other chains unexplained.

    TRM Labs. Original

  183. Reportedclaim Elliptic said whether the laundering automation involves AI agents rather than conventional scripts cannot be determined from the on-chain data.

    Elliptic. Original

  184. Reportedclaim Elliptic said the pattern of transactions suggests much of the laundering was carried out by software rather than by hand.

    Elliptic. Original

  185. Reportedclaim Elliptic said very few actors could coordinate an attack across 11 blockchains in around three hours.

    Elliptic. Original

  186. Reportedclaim Binance promised to cover all losses from company funds and allow clients to trade again within days after a record $6.3 billion hack.

    Yahoo Finance. Original

  187. Reportedclaim Binance stated that customer funds were safe and that it had located about $3 billion of the affected assets while working with partners to freeze them.

    Yahoo Finance. Original

  188. Reportedclaim Elliptic said the Binance theft closely resembles the Bybit theft, in which a developer's machine at the wallet provider Safe{Wallet} was compromised.

    Elliptic. Original

  189. Reportedclaim Binance co-CEO Yi He stated that the $3 billion in located assets represented only about 2% of the company's total user assets and public reserves.

    Yahoo Finance. Original

  190. Reportedclaim Elliptic reported that Richard Teng said in a video update that the attack was not carried out by one person.

    Elliptic. Original

  191. Reportedclaim Binance announced that its technical team was targeting a resumption of withdrawal services within approximately 34 hours.

    Yahoo Finance. Original

  192. Reportedclaim Elliptic said the attacker drained Binance hot wallets across 11 blockchains over a few hours.

    Elliptic. Original

  193. Reportedclaim Binance said it has set aside around $6.34 billion of company funds internally to cover the losses.

    Yahoo Finance. Original

  194. Reportedclaim Elliptic said funds stolen from Binance and from the Bitget exploit have been combined in several wallets, and that the link was first reported by ZachXBT.

    Elliptic. Original

  195. Reportedclaim Binance co-CEO Richard Teng described the breach as a complex attack involving a compromised laptop and malicious software designed to delete evidence.

    Yahoo Finance. Original

  196. Reportedclaim Elliptic said its total excludes a further $169 million that left Binance after withdrawals were suspended, which it described as appearing to be Binance moving its own funds.

    Elliptic. Original

  197. Reportedclaim Richard Teng explained that hackers manipulated a transaction approval system to move money from a hot wallet without passing through normal controls.

    Yahoo Finance. Original

  198. Reportedclaim Elliptic said $6.43 billion in cryptoassets was stolen from Binance on 29 October 2026.

    Elliptic. Original

  199. Reportedclaim British blockchain analysts Elliptic stated that the incident is almost certainly the single-largest-known theft of any kind.

    Yahoo Finance. Original

  200. Reportedclaim TRM Labs and Chainalysis noted that the heist bore similarities to previous large attacks blamed on North Korea.

    Yahoo Finance. Original

  201. Reportedclaim US President Donald Trump said he did not know if North Korean hackers were behind the theft but that his administration is looking into it.

    Yahoo Finance. Original

  202. Reportedclaim The FBI stated it is aware of the incident and is engaged with partners to understand the scope and coordinate investigative steps.

    Yahoo Finance. Original

  203. Reportedclaim Hacken said most of the money left in about 20 minutes, with a smaller second wave on Avalanche and Polygon around 23:05 UTC.

    Hacken. Original

  204. Reportedclaim The US Secret Service said its investigators are working with private-sector partners, including Circle, to identify, freeze, trace, and recover funds stolen from Binance.

    Yahoo Finance. Original

  205. Reportedclaim Hacken said nobody outside Binance knows whether a policy layer was set on the signing system, what it checked, or how the attacker obtained signatures.

    Hacken. Original

  206. Reportedclaim Abu Dhabi's Financial Services Regulatory Authority said it is engaging closely with Binance and monitoring the incident.

    Yahoo Finance. Original

  207. Reportedclaim Hacken said that at Binance the delegation stayed in place for 3 hours 46 minutes after the sweep and later deposits were swept again.

    Hacken. Original

  208. Reportedclaim The Guardian reported that cryptocurrency-related firms Coinbase, Strategy, and Robinhood fell in the wake of reports that hackers stole $6.3bn from Binance.

    The Guardian. Original

  209. Reportedclaim The Guardian reported that Binance has said the attack began with a compromised employee laptop and involved multiple breach points, that it found no evidence of private-key leakage, and that it said roughly $3bn of affected assets had been frozen.

    The Guardian. Original

  210. Reportedclaim Experts such as TRM Labs attributed the $6.3bn Binance cryptocurrency theft to the North Korean hacking unit TraderTraitor, also known as the Lazarus Group.

    The Guardian. Original

  211. Reportedclaim Binance pledged to meet customer losses through its SAFU reserve and company resources, announcing more than $6.34bn of company funds separate from roughly $3bn of frozen assets.

    The Guardian. Original

  212. Reportedclaim Elliptic, a consultancy specialising in crypto-related crime, stated that the incident could be the biggest heist of any kind in history and is more than four times bigger than the previous largest crypto hack.

    The Guardian. Original

  213. Reportedclaim CFTC chairman Michael Selig told reporters that the CFTC has the ability to trace the incident in the blockchain and that it is very concerning that there have been several cyber incidents involving crypto.

    The Guardian. Original

  214. Reportedclaim Hacken said Binance's statement that no private key leaked and investigators' view that Binance's signing system signed for the attacker can both be true.

    Hacken. Original

  215. Reportedclaim Hacken recommended that wallet operators cap value and rate per wallet at the signer and hold new destinations for a second approval.

    Hacken. Original

  216. Reportedclaim Hacken said early signs on Ethereum pointed to phishing of the authorizations, which could explain Ethereum but none of the other chains.

    Hacken. Original

  217. Reportedclaim Hacken, quoting investigators, said the most likely explanation is that the attacker gained the ability to make Binance's hot wallet signing system sign transactions of its choosing across chains.

    Hacken. Original

  218. Reportedclaim Blockaid said the delegation was visible on-chain for three minutes and 24 seconds before the sweep.

    blockaid.io. Original

  219. Reportedclaim Blockaid said its detection flagged the drain under two minutes after the sweep and before any public report.

    blockaid.io. Original

  220. Reportedclaim Blockaid said its transaction security engine classified the delegation transaction as malicious because an EOA was being upgraded through EIP-7702 to an untrusted address.

    blockaid.io. Original

  221. Reportedclaim NPR reported that Kok Tin Gan of NyxLab said the event raises questions about why stronger approval controls were not in place.

    npr.org. Original

  222. Reportedclaim WIRED reported, citing TRM Labs, that the majority of the stolen crypto was taken in around 20 minutes on 29 October.

    WIRED. Original

  223. Reportedclaim WIRED reported, before the FBI statement, that neither Binance nor law enforcement officials had named suspected links to North Korean hackers.

    WIRED. Original

  224. Reportedclaim The BBC reported that crypto history watchers online were pointing out that Binance's message that customer funds will be covered resembles a message given by the FTX CEO before FTX collapsed in 2022.

    BBC News. Original

  225. Reportedclaim TRM Labs wrote that Binance said it was investigating a potential security issue, then said it had temporarily suspended withdrawals on multiple networks as a precaution, and that Binance has said user funds are safe.

    TRM Labs. Original

  226. Reportedclaim The BBC reported that several experts warned customers not to regard Binance's promise to cover losses as legally binding.

    BBC News. Original

  227. Reportedclaim Binance co-CEO Yi He said Ripple helped stop about USD 200 million from moving; TRM reports a 40.5M RLUSD freeze; the sources do not say whether the figures measure the same thing.

    TRM Labs. Original

  228. Reportedclaim The BBC reported that Binance had initially suspended all deposits and withdrawals but then said in an update that deposits remain unaffected.

    BBC News. Original

  229. Reportedclaim The BBC quoted Binance co-CEO Richard Teng as saying this was not carried out by one person.

    BBC News. Original

  230. Reportedclaim The BBC described TraderTraitor as also known as the Lazarus Group.

    BBC News. Original

  231. Reportedclaim BleepingComputer reported that Binance warned customers to remain cautious of scams and avoid unofficial links, messages, or requests for account information.

    BleepingComputer. Original

  232. Reportedclaim Cointelegraph reported that Richard Teng said the attacker used a self-destruct mechanism to destroy tools and traces, complicating the investigation.

    Cointelegraph. Original

  233. Reportedclaim Cointelegraph reported that Binance said it submits weekly reports on company funds to Abu Dhabi's Financial Services Regulatory Authority under a requirement that predated the hack.

    Cointelegraph. Original

  234. Reportedclaim Cointelegraph reported at 00:07 UTC on 30 October that Binance said it had temporarily suspended deposits.

    Cointelegraph. Original

  235. Reportedclaim Cointelegraph reported that Richard Teng wrote that Binance's investigation has not attributed responsibility to any individual.

    Cointelegraph. Original

  236. Reportedclaim Cointelegraph reported that ZachXBT said this indicates the same actor is likely behind both incidents.

    Cointelegraph. Original

  237. Reportedclaim Binance announced on X that the first batch of networks opened in phase one of withdrawals is the Bitcoin network.

    Cointelegraph. Original

  238. Reportedclaim Cointelegraph reported that Blockaid CEO Ido Ben-Natan said attackers could have stolen the funds without EIP-7702.

    Cointelegraph. Original

  239. Reportedclaim CertiK told Cointelegraph on Friday that it needed more information to verify Binance’s claimed $5 billion in replacement cryptocurrencies.

    Cointelegraph. Original

  240. Reportedclaim Cointelegraph quoted Ido Ben-Natan as saying the 7702 upgrade is a way to do this in one sweep and maybe a way to bypass some sort of checks they may have.

    Cointelegraph. Original

  241. Reportedclaim Glassnode reported that the Binance breach was the largest cryptocurrency hack on record with around $6.3 billion affected, exceeding the combined losses from the next nine largest hacks. The same passage gives the previous record as the $1.5 billion Bybit exploit in February 2025.

    Cointelegraph. Original

  242. Reportedclaim Cointelegraph reported that Ethereum community member VEER said EIP-7702 gave attackers a handy sweep button on Ethereum.

    Cointelegraph. Original

  243. Reportedclaim Blockaid CEO Ido Ben-Natan stated that the attackers appeared to have compromised Binance’s transaction signing process.

    Cointelegraph. Original

  244. Reportedclaim Cointelegraph reported that Ambire CEO Ivo Georgiev said EIP-7702 made little difference because the hackers already had the ability to authorize transactions.

    Cointelegraph. Original

  245. Reportedclaim Cointelegraph quoted Ido Ben-Natan as saying that ultimately the signer signed a transaction that they shouldn't have.

    Cointelegraph. Original

  246. Reportedclaim Cointelegraph reported that approximately $3 billion in frozen assets and Binance's $1.17 billion emergency fund could cover about 66% of the reported losses, leaving a potential $2.1 billion gap.

    Cointelegraph. Original

  247. Reportedclaim Cointelegraph reported that Nansen said it could not verify what funds Binance had available beyond its roughly $1.16 billion emergency fund.

    Cointelegraph. Original

  248. Reportedclaim Cointelegraph reported that CertiK said it needed more information from Binance to assess whether the claimed $5 billion in matching tokens could be independently verified on-chain.

    Cointelegraph. Original

  249. Reportedclaim Cointelegraph reported that Changpeng Zhao said Binance's SpaceX holdings alone were worth more than $1 billion.

    Cointelegraph. Original

  250. Reportedclaim Cointelegraph reported that Yi He said the exchange's revenue for the year was sufficient to cover the hack losses and that the company did not need to sell its stake in SpaceX.

    Cointelegraph. Original

  251. Reportedclaim Cointelegraph reported that Changpeng Zhao said Gulf, Binance's partner in Thailand, had offered financial support.

    Cointelegraph. Original

  252. Reportedclaim Cointelegraph quoted a Binance spokesperson as saying the $5 billion is held in the exact token assets required and is in Binance custody.

    Cointelegraph. Original

  253. Reportedclaim Cointelegraph reported that a Binance spokesperson did not specify how much each funding source contributed or disclose the insurance fund's minimum required balance.

    Cointelegraph. Original

  254. Reportedclaim Cointelegraph reported that Binance ranks as the largest exchange by reserves with $134 billion in total assets.

    Cointelegraph. Original

  255. Reportedclaim Cointelegraph reported that Bitcoin traded near $77,400 on Saturday, about 4% below its price shortly before the attack began.

    Cointelegraph. Original

  256. Reportedclaim Cointelegraph reported that the hack's effect on crypto markets was compounded by tech-stock losses tied to Q4 earnings projections.

    Cointelegraph. Original

  257. Reportedclaim Cointelegraph reported that crypto company shares fell sharply on Friday, with Coinbase down more than 13% a day after reporting lower third-quarter revenue.

    Cointelegraph. Original

  258. Reportedclaim Cointelegraph quoted Cynthia Lummis as saying the Clarity Act would have given crypto firms legal cover to freeze suspicious transactions the instant law enforcement calls.

    Cointelegraph. Original

  259. Reportedclaim Cointelegraph quoted Michael Selig as saying "This proves our exact point in proposing regulations for crypto markets."

    Cointelegraph. Original

  260. Reportedclaim Cointelegraph reported that it was not clear whether there was any immediate political advantage to be gained from the hack, but that Republican and Democratic sides began staking out positions almost immediately.

    Cointelegraph. Original

  261. Reportedclaim Cointelegraph reported that political and administration figures began offering opinions on the hack with a US election approaching on 3 November.

    Cointelegraph. Original

  262. Theoryclaim A Hacker News commenter commented that the hack was almost certainly an inside job given the knowledge of Binance systems required.

    Hacker News. Original

  263. Reportedclaim Cointelegraph quoted Cynthia Lummis as saying that hackers stole more than $6 billion from Binance in less than 4 hours, the biggest heist in history.

    Cointelegraph. Original

  264. Reportedclaim The BBC reported that Binance said in 2024 that it had more than $160bn in assets under its custody.

    BBC News. Original

  265. Reportedclaim The Guardian live blog described TraderTraitor as having emerged from Lazarus, a group working from North Korea's Reconnaissance General Bureau.

    The Guardian. Original

  266. Reportedclaim The Guardian reported that Bitget said in September that roughly $350m in crypto had been stolen from its platform.

    The Guardian. Original

  267. Reportedclaim The BBC reported that a hack on the crypto exchange Bitget in September lost $388m.

    BBC News. Original

  268. Reportedclaim Cointelegraph reported that frozen funds do not necessarily equal recovered funds, because freezing stops attackers spending them but does not automatically return them to Binance or its users.

    Cointelegraph. Original

  269. Officialclaim Binance said on 1 November that it will bear the financial impact of the stolen funds and that the losses will not be passed on to users.

    Binance. Original

  270. Officialclaim Binance said on 31 October that the outstanding 10% consisted of tokens outside the ten largest listed.

    Binance. Original

  271. Reportedclaim Cointelegraph reported that LlamaRisk said the exploiter deposited 60 million USDT into Aave and borrowed 19,762 WETH worth about $44.6 million at the time.

    Cointelegraph. Original

  272. Reportedclaim Cointelegraph reported at 21:15 UTC on 29 October that Binance was investigating a potential multibillion-dollar security breach after suspicious transfers prompted Tether and Circle to reportedly freeze billions.

    Cointelegraph. Original

  273. Theoryclaim A Hacker News commenter commented 'My money is on an inside job.'

    Hacker News. Original

  274. Theoryclaim A Hacker News commenter commented that North Korea is a convenient target to blame instead of highlighting random insiders as the actual cause.

    Hacker News. Original

  275. Theoryclaim A Hacker News commenter asked whether there was actually a hack into Binance systems or just an insider or credential leak.

    Hacker News. Original

  276. Theoryclaim A Hacker News commenter commented that the timing of a separate software supply chain attack was not a coincidence.

    Hacker News. Original

  277. Theoryclaim A Hacker News commenter replied that the actors behind that supply chain attack did not seem to have the skills to reach a full Binance compromise within hours.

    Hacker News. Original

  278. Theoryclaim A Hacker News commenter corrected an earlier suggestion, writing that a DebugBear compromise was related to the Polymarket security incident, not Binance.

    Hacker News. Original

  279. Theoryclaim A Hacker News commenter wrote that DebugBear is related to the Polymarket hack, not Binance.

    Hacker News. Original

  280. Theoryclaim A Hacker News commenter commented that picking politically attractive proxy scapegoats is a classic move.

    Hacker News. Original

  281. Reportedclaim Wikipedia says Coincheck was hacked in January 2018 and approximately 500 million NEM tokens ($530 million) were stolen.

    Wikipedia. Original

  282. Reportedclaim Wikipedia says some $473 million in funds were later taken from FTX in an unauthorized transaction.

    Wikipedia. Original

  283. Reportedclaim Wikipedia says the Poly Network exploit was an attack by anonymous hackers on 10 August 2021 that transferred over $610 million in digital assets.

    Wikipedia. Original

  284. Reportedclaim Wikipedia says that in March 2022 hackers compromised the Ronin Network and stole approximately US$620 million worth of cryptocurrency.

    Wikipedia. Original

  285. Reportedclaim TRM Labs said that on the nine chains other than Ethereum, Binance wallets sent funds to the attacker through ordinary signed transfers.

    TRM Labs. Original

  286. Reportedclaim The Block reported that Chainalysis said an AI-assisted hacker breached its systems and accessed non-sensitive customer data including names and emails.

    The Block. Original

  287. Reportedclaim The Block reported that Chainalysis said its own breach is not related to the Binance theft.

    The Block. Original

  288. Reportedclaim Cointelegraph reported Binance's exchange reserves as $165 billion, including assets backing customer balances.

    Cointelegraph. Original

  289. Theoryclaim A Hacker News commenter wrote that a risk management system should not let $5bn be transferred instantly, and wondered whether it was an inside job.

    Hacker News. Original

  290. Reportedclaim Cointelegraph reported that a Binance spokesperson declined to disclose wallet addresses, citing security reasons, and that Binance did not disclose when it acquired the assets.

    Cointelegraph. Original

  291. Reportedclaim Cointelegraph quoted Ido Ben-Natan as describing "a compromise of signing infrastructure" and saying "We don't think a key was leaked."

    Cointelegraph. Original

  292. Reportedclaim Tom Robinson of Elliptic stated that North Korea is likely responsible for the hack.

    WIRED. Original

  293. Reportedclaim TRM Labs stated that the attacker deployed code and tested it on wallets early on October 29 before installing it on a Binance hot wallet four hours later.

    WIRED. Original

  294. Reportedclaim Tom Robinson of Elliptic stated that Binance says the attack began with a compromised engineer's laptop, which is a hallmark of TraderTraitor.

    WIRED. Original

  295. Reportedclaim Tom Robinson of Elliptic stated that the remaining $3.3 billion is mostly Bitcoin, Ether, and XRP, which cannot be frozen.

    WIRED. Original

  296. Reportedclaim Cointelegraph said that the attack, described as the largest in crypto history, began at 8:04 pm UTC on Thursday and that the perpetrators were linked to North Korean hackers.

    Cointelegraph. Original

  297. Reportedclaim Cointelegraph reported that CertiK engineer Dickson Wu traced $500 million in USDT that was sent to one address, with $325 million sold to market makers for ETH by 20:59 UTC, less than an hour after the hack began.

    Cointelegraph. Original

  298. Reportedclaim LlamaRisk reported that the attacker’s position on Aave held around $59.9 million in USDT collateral against $43.8 million in debt, and Aave stated the position remained overcollateralized.

    Cointelegraph. Original

  299. Reportedclaim Marc Zeller, founder of the Aave Chan Initiative, said USDT is real money backed by dollars and that the position is criminal but overcollateralized in the eyes of the protocol.

    Cointelegraph. Original

  300. Reportedclaim Elliptic estimated that $2.84 billion had been frozen by 7:00 am UTC on Friday, while the attackers still controlled around $3.33 billion in assets that issuers could not immobilize.

    Cointelegraph. Original