Anmelden

Learn Crypto Podcast

Binance Hack: $6.3B Incident and the DevOps Laptop Claim

Freitag, 30. Oktober 2026 · 10 min

MP3

Shownotes

A fast-moving security incident affecting Binance-linked wallets was still developing when this episode was recorded. Peter walks through reports of multi-chain outflows, Binance's public updates, and its statement that roughly US$3 billion had been frozen while the estimated impact had risen to about US$6.3 billion.

The episode reconstructs the reported timeline, explains why Tether and Circle freezes mattered, and separates Binance's initial DevOps-laptop explanation from facts that still require a full technical post-mortem. It also covers practical phishing precautions and the risks of concentrating assets with one exchange or wallet provider.

Figures and causes in this episode reflect the sources available during recording and may change as Binance, issuers and investigators publish verified updates. Check official Binance channels before acting on any message or security claim.

Chapters:
Binance Hacked
Polymarket and Tampered Ledger Wallets
The Timeline of the Hack
Tether and Circle Freeze Funds
What's Moving Out
Binance's Official Response
Watch Out for Phishing Emails
About $3 Billion Frozen
Yi He: Binance Will Cover All Losses
Remember FTX?
Can Binance Cover It?
Update: A Compromised DevOps Laptop
Wrap Up
Spreading the Risk: OneKey and Tangem

What you'll learn:
- Binance said its initial investigation suggested a compromised DevOps engineer's laptop may have enabled unauthorised withdrawal transactions, while stressing that the investigation was not complete.
- Binance's update put the estimated impact at about US$6.3 billion and said roughly US$3 billion had been frozen on-chain at the time of recording.
- Tether and Circle were reported to have frozen substantial USDT and USDC amounts as issuers and investigators traced affected assets.
- Binance said it would cover losses using the SAFU fund and company funds, but those assurances still require verification against the promised post-mortem and updated proof of reserves.
- Users should verify urgent security messages against official Binance channels and avoid clicking unexpected email links during a high-profile incident.
- The episode discusses spreading custody risk across suitable providers rather than assuming any exchange, software wallet or hardware wallet is immune from compromise.
- OneKey supplied the Classic wallet mentioned near the end of the episode; Peter says any later comparison will be a detailed, honest review.

References:
- X trending context: Binance incident — link.learncardano.io/U... (link.learncardano.io/U0tzv6)
- X trending context: related security reports — link.learncardano.io/l... (link.learncardano.io/lLRanR)
- X trending context: incident updates — link.learncardano.io/2... (link.learncardano.io/2Bf9Qw)
- Initial incident timeline shared on X — link.learncardano.io/P... (link.learncardano.io/PJUqfI)
- Watcher.Guru asset-flow report — link.learncardano.io/z... (link.learncardano.io/zI0rtR)
- Binance official incident statement — link.learncardano.io/M... (link.learncardano.io/MHcMNx)
- Binance official frozen-funds update — link.learncardano.io/Q... (link.learncardano.io/Q889j0)
- Yi He statement on covering losses — link.learncardano.io/q... (link.learncardano.io/q77ocX)
- Community discussion and solvency questions — link.learncardano.io/o... (link.learncardano.io/okNg2k)
- Binance initial investigation update — link.learncardano.io/4... (link.learncardano.io/40siSn)

OneKey supplied the Classic wallet mentioned in the episode. No claim of paid sponsorship is made.

Figures and causes were developing at recording time. Verify updates through official Binance channels. This content is educational only and is not financial advice.

Learn more: link.learncardano.io/b... (link.learncardano.io/bQ68Rc)
Subscribe: link.learncardano.io/u... (link.learncardano.io/u6BDgr)

DISCLAIMER: This content is for informational and educational purposes only and is not financial, investment, or legal advice. I am not affiliated with, nor compensated by, the project discussed—no tokens, payments, or incentives received. I do not hold a stake in the project, including private or future allocations. All views are my own, based on public information. Always do your own research and consult a licensed advisor before investing. Crypto investments carry high risk, and past performance is no guarantee of future results. I am not responsible for any decisions you make based on this content.

🔗 youtube.com/watch?v=Fq8FhvxET2k

Subscribe to the audio podcast:
🔗 bit.ly/learncardano-spotify
🔗 apple.co/3jEPM8C
🔗 learncardano.io

Follow on Social:
🔗 x.com/learncardano
🔗 facebook.com/learncardano

Transkriptvom Podcast bereitgestellt · Zeitmarken springen hin

All right, guys, we've got a massive developing story here around Binance and the potential hack, or it does look like a hack. And we're seeing almost $ 5. 6 billion being hacked from the exchange. And this is the timeline that we have at the moment. Funds have been frozen across multiple different chains and a lot of USDT, USDC has been blocked from moving. So that is definitely a good thing.

But let's have a look at the details here. So this is a headline that we're seeing. On-chain data revealed outflow totaling up to 5.7 billion across Ethereum, Bitcoin and Tron from Binance linked wallets, including a huge 167,000 ETH transfer tied to Tornado Cash. So that's the main headline that we're seeing at the moment. And I'm just pulling together some other tweets and posts that are coming out on X at the moment to try and work out what's happening. But along with this, We're also seeing Polymarket hacked, drained for $ 2. 6 million. And we're seeing reports now from Singapore to around the number of tampered Ledger wallets stealing millions in that space there and what's been happening there.

And they've reported about $ 3. 5 million being hacked across those Ledger hardware wallets. So we're not out of the woods at the moment. It is definitely not safe to be in the crypto space, whether you're on a centralised exchange or decentralised wallets. or even holding in a cold wallet, which you suspect should be safe, but no, it's not at the moment. So this is what I found from the timeline in regards to what's happening at the moment.

On the 28th, a wallet gets funded through Tornado Cash. On the 29th at 4pm UTC, it deploys a malicious contract. At 8.20 UTC, Binance Hot Wallet 14 signs a permission pointing to it. At 8.24 UTC, Transaction 1 sweeps the wallet, 14, and 167 ETH gets transferred and 1.6 billion USDT. 24 seconds later, wallet 16 sends 28,000 ETH to the same address.

At 8.42, 780 million USDC leaves wallet 34. At 8.45, BTC drops 2,500 in one candle. and 627 million in longs are completely wiped. So if you are tracking charts, this is probably why you're seeing the big drops at the moment. At 9.11, Tether starts freezing 1.567 billion USDT locked, and at 9.13, Circle freezes 823 million USDC. At 9.15, CZ Binance says it does look like a hack. And at 9.29, Binance states that users' funds are completely safe.

Another 200 million USDT drain since and still ongoing. So that's the timeline that we're seeing at the moment. A lot of assets being moved out. I think it's been about four or five hours since this has all started and it's still ongoing. We've got a post here from Watcha Guru tracking what assets and how much of these assets are moving out. The biggest one there that you can see is that 1.45 billion BTC and the 875 million of the ETH. So you can see all these assets are moving out at the moment. But thankfully, a lot of this is being frozen. Hopefully, we don't see it all being liquidated on the markets. This is the official announcement from Binance about an hour and a half ago.

We're working nonstop to resolve this issue. Binance will cover all losses. As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freeze funds, and work with law enforcement. We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates.

And this is an industry-wide effort, and we are grateful for our partners across the ecosystem who have moved quickly to help freeze affected assets. We will continue to share verified updates through official Binance channels. User funds are safe. So please guys, if you are monitoring this, if you do have funds on Binance, make sure you follow the official channels. If you get emails from Binance, double check on X to see if that information in the email actually matches up with what's happening on X. I'll be very cautious on clicking anything that is being sent directly to your email at the moment because it's Other scammers may be jumping in right now, seeing this big announcement come out and then start sending out phishing email campaigns

that are trying to get access to your Binance funds or your crypto wallets or whatever it might be. So be extremely cautious with what's happening at the moment. Now, this is another update that came out from Binance just about an hour ago. So update the current verified total frozen amounts is around 3 billion. So out of that 5.7, 3 billion now has been frozen. Our teams continue to work closely with law enforcement issuers, blockchain intelligence firms, and industry partners to trace and freeze additional assets. And this post here comes from Yi He, co-founder and chief customer service officer at Binance. And she states that Binance will cover all hacking losses. Now, this here is something that

was stated when FTX crashed not many years ago. I think it was a few years ago now. It just feels like ages ago. But the exchanges since then, from what I've been told, do have a lot more backup and safety funds in case this ever did happen again. Whether exchange collapses, whether there's a run on the exchange, whether a big hack like this happens, the exchanges, from what I've been told, have been putting away a lot of funds. So let me just go down here a little bit further. And here you can see other people in the comments here being very skeptical of the exchange actually having their funds and being able to cover all of the assets that were being stolen. But from what I've been told and what I completely understand from the

industry since FTX, they have made huge efforts to ensure that they do have the funds to cover from massive hacks like this or massive collapses that may happen in the industry. We have a very volatile industry in the crypto space. So having the extra funds to cover any things like this that may happen because we don't have insurance like many banks do to cover collapses. So from what I understand, that is how the industry has changed since FTX. And I do believe personally that Binance do have the funds to cover any of these hacks. The fact that there has been approximately $ 3 billion of the funds being frozen at the moment, which means they can get those funds back eventually, that $ 3 billion. But then

the other $ 2 billion is what they need to cover in terms of losses. But they may be able to recover more. So hopefully, we do see that last $ 2. 7 billion also recovered and they don't need to cover it from their own funds. Now, while recording this, another announcement had come out from Binance. And this is very concerning here.

So let me just read you out this updated report. Binance initial investigation suggests that the security incident may have involved a compromise between DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We found no evidence of any wallet private key leak. We will share details technical postmortem once investigation is complete and the facts are fully verified. The estimate impact sits at around $ 6. 3 billion, so the number has gone up. We have worked with blockchain partners to freeze affected assets with $ 3 billion frozen on-chain so far.

Binance will cover all losses and the Seifu Fund and the company's funds. User funds are safe. We will also publish updated proof of reserves once remediation is complete. So it's kind of crazy here to see that one DevOps engineer's laptop could have been a source of this potential compromise. Very scary indeed, but we'll find out more once the investigation is done and the report is put up. All right, guys, that's all I got for this particular update. This is a developing story and I'll keep you guys up to date with what I find out as well. So if you want to be kept up to date via YouTube here, make sure you hit that thumbs up, like, subscribe and notification bell. I will be looking at other hardware wallet alternatives.

I used to have a ledger. I used to have a keystone and use them on a regular basis, but I'm looking at my other options now to see what's available. I'm playing around with this one here. I just got this one the other day. The OneKey team sent me this one, so I'll be checking out this wallet to see how it works. It's a classic, so I think that's the cheap one. And then I also got this Tangent wallet here. This is the physical card one as well.

It looks quite nice, but I'll be checking out those ones there to see how these ones compare to Ledger, Keystone, and all those other hardware wallets out there, because we kind of need to look for alternatives so we can spread out assets and you know if one gets compromised you still have assets on another so kind of decentralizing your risk and it kind of makes sense but i'll be looking to those ones and be giving detailed honest reviews as well anyway like i said guys hit that thumbs up on the way out youtube memberships down below buy me a coffee links there as well great ways to support the channel otherwise try and keep positive guys and i'll see you in the next video Thank you.

Anmelden oder registrieren

Jetzt

0:00 / 0:00