Latest / The Cross Border Report / The $6.3 Billion Binance Heist: Inside Crypto's Biggest Theft
Transcript
- 0:00SPEAKER_00: Welcome to another episode of the Cross Border Report, where we explore the intersection of global finance, geopolitics, risk, and regulation.
- 0:07SPEAKER_00: I'm your host, Brad Gullet.
- 0:09SPEAKER_00: And today we're going to be talking about the recent Binance hack.
- 0:12SPEAKER_00: By now most have heard of it, some really eye-popping numbers.
- 0:17SPEAKER_00: But I think fundamentally, you know, most people approach this from different angles, right?
- 0:23SPEAKER_00: The one that I'm curious about, and the one that you may be curious about, is how does an organization that specializes in securing billions of dollars in cryptocurrency lose control of its own transaction authorization systems, right?
- 0:35SPEAKER_00: And so the question sort of betrays a little bit of the um the what happened, right?
- 0:41SPEAKER_00: And we'll get into that a little bit.
- 0:43SPEAKER_00: But fundamentally, I think that's the core, the core angle that we want to take here in this discussion today, right?
- 0:49SPEAKER_00: And so just a just a few highlights.
- 0:52SPEAKER_00: Don't want to go too much in depth as far as what you know um you know what happened.
- 0:57SPEAKER_00: Um, there's a long write-up online, um, different different outlets and and Binance themselves have have uh you know kind of spoken to it.
- 1:06SPEAKER_00: Um, but just some of the high levels.
- 1:08SPEAKER_00: So um this was effectively a cybercrime um you know north perpetrated by a North Korean uh entity um uh uh impacting crypto custody, right?
- 1:19SPEAKER_00: So like that's those are kind of like the the high level points.
- 1:22SPEAKER_00: Um it's being reported as the largest cryptocurrency theft in history um and potentially the largest financial heist ever.
- 1:29SPEAKER_00: Um I'm not sure about that last claim, um, but it did uh impact approximately$6.3 billion uh in worth of crypto.
- 1:38SPEAKER_00: So um whatever whatever the the the factoid might be, um it's a lot of money.
- 1:43SPEAKER_00: Um and so you know, kind of what happened and then how we're thinking about it, right?
- 1:47SPEAKER_00: So um the attack began on October 29th um with attackers moving uh the crypto from wallets associated with the exchange.
- 1:55SPEAKER_00: Um it affected wallets across 10 blockchain blockchain networks uh with the majority of the theft uh occurring in about 20 minutes, um, according to some reporting online.
- 2:05SPEAKER_00: Um and Binance themselves, actually.
- 2:08SPEAKER_00: Um, they put out a great statement on X that that kind of walks through it um end to end, which I thought was really was really a great um a great summary uh and beneficial to others in the in the space.
- 2:20SPEAKER_00: Um but anyway, uh Binance temp, so what they came out and said that they had temporarily suspended withdrawals.
- 2:26SPEAKER_00: Um, they began coordinating with blockchain companies and stablecoin issuers to free stolen assets um and announced that they would cover the customer losses.
- 2:33SPEAKER_00: Um and so uh according to their statement on October 29th, um, that was posted on X, um, it's it sounds like they've replenished approximately 98% of funds.
- 2:43SPEAKER_00: And today is November 5th, as I'm recording it.
- 2:46SPEAKER_00: So they may they may have done even more than that since then.
- 2:49SPEAKER_00: Um, but that's what they reported by then.
- 2:51SPEAKER_00: Um interesting note here previous record setting crypto theft was the February 2025 Bybit attack involving approximately 1.5 billion.
- 3:01SPEAKER_00: Um and that's something I found online.
- 3:03SPEAKER_00: So again, I didn't independently verify that, but I I found that number to be interesting.
- 3:06SPEAKER_00: So if this is a magnitude of you know four or five times that, um that's quite remarkable.
- 3:11SPEAKER_00: Um so a little bit about what happened.
- 3:14SPEAKER_00: So they they compromised the systems that authorized crypto transactions, essentially.
- 3:18SPEAKER_00: Um and and and this is according to Reuters, it was apparently a months-long operation involving compromised employee devices, social engineering, malicious developer software, and Binance's internal wallet infrastructure.
- 3:30SPEAKER_00: Um, and again, I did go through Binance's the full uh release they did on X on October 29th.
- 3:36SPEAKER_00: It it provides some really interesting detail um about how it was a multi-phased attack that um compromised uh more than one uh employee of Binance.
- 3:48SPEAKER_00: Uh, it's really very sophisticated um as far as what actually happened.
- 3:53SPEAKER_00: Um and in looking at the actual timeline, so it looks like June 2026, there was an initial compromise.
- 3:59SPEAKER_00: Um according to Binance, a wallet team employee downloaded a tampered software package while searching for an AI tool.
- 4:06SPEAKER_00: Um that device was subsequently detected and replaced, but the attackers have basically already established themselves in the network, in the company's environment.
- 4:14SPEAKER_00: Um and then in September, a fake recruitment campaign.
- 4:18SPEAKER_00: So a second employee was approached through a legitimate employment platform.
- 4:21SPEAKER_00: Um the attackers impersonated recruiters and company executives, uh, conducted video interviews, and um ultimately provided a coding assignment that contained malicious software.
- 4:31SPEAKER_00: Um so that was uh that was the next piece.
- 4:34SPEAKER_00: Um once they're in the system, essentially, the attackers use the compromise devices and an internal AI tool to reach systems belonging to wallet developers.
- 4:44SPEAKER_00: Um, you know, it's particularly interesting from a corporate security perspective, um, given the the attack leveraged you know trusted internal tools and employees access rather than uh you know simply attacking um you know an externally exposed uh uh piece of the uh piece of crypto application, right?
- 5:03SPEAKER_00: Um it was in you know leveraging internal tools.
- 5:06SPEAKER_00: So again, very sophisticated, uh multifaceted.
- 5:09SPEAKER_00: Um and then October 29th is kind of when the when it started the execution.
- 5:13SPEAKER_00: Um they used stolen credentials to deploy uh malicious script and initiate unauthorized transactions.
- 5:20SPEAKER_00: Um it's it looks like Binance detected large transfers and began attempting to contain the incident, right?
- 5:27SPEAKER_00: So on the next day, October 30th, you had containment.
- 5:30SPEAKER_00: So Binance and partners began freezing affected assets and restricting withdrawals.
- 5:35SPEAKER_00: Um by then the attackers had moved a substantial amount of cryptocurrency across multiple networks.
- 5:40SPEAKER_00: So um, you know, not a techno technologist by trade, um, but uh, but it it this is fascinating to me.
- 5:47SPEAKER_00: Was I, you know, in studying kind of what happened um and applying it to um you know the you know the work environment, it's it is interesting to see kind of how um this all unfolded, um, even for one that's not, you know, and I'm not in the the you know um information security space, but it very interesting as far as um you know cause-effect relationship, causality, what what happened, risk mitigation, that sort of thing.
- 6:13SPEAKER_00: Um some other pieces, um and we mentioned it a little bit briefly, but the FBI directly attributed it to a North Korean hacking group uh known as Traitor Traitor, um, which they of course denied.
- 6:25SPEAKER_00: Um TRM Labs um also they they came out and attributed a high level of confidence that it was that group.
- 6:33SPEAKER_00: Um also according to TRM Labs, the the attackers compromise the ballots, the Binance's wallet signing infrastructure, right?
- 6:41SPEAKER_00: So it's from different places you you're you're seeing different people kind of um speak to what happened.
- 6:48SPEAKER_00: Um very interesting.
- 6:50SPEAKER_00: Um again, there's deeper write-ups online um kind of about what happened.
- 6:55SPEAKER_00: And when I plugged it into AI, just kind of asked it um, you know, thoughts on it, but you know, what it saw, better summary sort of thing.
- 7:03SPEAKER_00: Um the LLM explained it to me this way.
- 7:06SPEAKER_00: Um, imagine a bank has a vault that requires multiple employees to authorize a withdrawal.
- 7:10SPEAKER_00: The bank has invested heavily in protecting the vault keys, but an attacker compromises the system those employees use to authorize withdrawals.
- 7:19SPEAKER_00: Um, the attacker may not need to physically steal the keys.
- 7:22SPEAKER_00: Uh they may be able to manipulate the authorization process itself.
- 7:26SPEAKER_00: That's the distinction between protecting the vault and protecting the system that controls the access to the vault.
- 7:32SPEAKER_00: Again, that's from AI.
- 7:33SPEAKER_00: It's not my own words from AI, but it's interesting, right?
- 7:35SPEAKER_00: It's an interesting summary, um, you know, in layman's terms, uh, you know, for folks like myself about what actually happened.
- 7:43SPEAKER_00: Um, you know, and and interestingly enough, you know, it includes devices, credentials, software, and processes that authorize transactions, right?
- 7:52SPEAKER_00: It include all of those things.
- 7:54SPEAKER_00: Um and so it was certainly an interesting, um, an interesting lesson from different aspects.
- 8:02SPEAKER_00: Um, and and cryptocurrency theft in general um, you know, can provide a source of funds outside conventional banking, um, assets that can be moved across jurisdictions quickly, opportunities to convert stolen cryptocurrency into other assets, and a potential route to evade traditional financial controls, right?
- 8:19SPEAKER_00: So, you know, we've talked a lot about crypto in the past, um, some of the benefits, some of the drawbacks.
- 8:24SPEAKER_00: Those are some of the risks, right?
- 8:26SPEAKER_00: Um, particularly around theft um and kind of what what happens there, right?
- 8:32SPEAKER_00: It's there's a lot of there's a lot of risk in that system um or in systems that leverage that sort of infrastructure.
- 8:38SPEAKER_00: And so it's important to kind of dissect um, you know, where what what the risks are, call them out by name, and then um, you know, might be able to better understand it that way.
- 8:47SPEAKER_00: Now, for those in banking or are mitigating um you know traditional fiat risk or uh money movement risk, um why why one one sort of question right that stands out, why freezing crypto is different from freezing a bank account, right?
- 9:02SPEAKER_00: So this is kind of an application question, right?
- 9:04SPEAKER_00: So we're transitioning from you know the kind of what happened to, well, how does it translate, right, from a from a traditional risk controls perspective, right?
- 9:12SPEAKER_00: Um, well, some stable coins, including USDT and USDC, have issuer-controlled functions that can allow the issuer to freeze tokens, right?
- 9:21SPEAKER_00: So that's the first way it might differ.
- 9:23SPEAKER_00: Um essentially, it means that a cryptocurrency transaction can be technically successful in a blockchain while the recipient's assets subsequently become inaccessible.
- 9:32SPEAKER_00: Um in this case, blockchain intelligence firms reported that the stablecoin issuers and other ecosystem participants froze substantial amounts of assets.
- 9:42SPEAKER_00: Um, and then the attackers also attempted to convert the stable coins into other assets, including Ethereum, to move funds beyond the reach of issuer level freezing.
- 9:51SPEAKER_00: Um TRM reported that approximately 2.7 billion in assets have been frozen through stablecoin issuers and other blockchain ecosystem uh intervention interventions in its initial analysis.
- 10:02SPEAKER_00: Um that's interesting, right?
- 10:04SPEAKER_00: Again, that's that these are points that um you know, again, in reading the article and probing AI that kind of helped me put together how is it different, right?
- 10:13SPEAKER_00: I was trying to figure it out for myself.
- 10:16SPEAKER_00: Um, you know, as I study crypto deeper and understand the risks associated with the space, you know, I I was curious myself, how how is it different?
- 10:24SPEAKER_00: And that's that's kind of the conclusion that I was coming to, and um, you know, with the assistance of what I was reading and and and with LLM, of course, um kind of putting it all together.
- 10:35SPEAKER_00: Um but it's interesting, right?
- 10:37SPEAKER_00: Um, and and and I think uh another interesting discussion point is that cryptocurrency in being decentralized at the blockchain level, but the surrounding financial ecosystem not necessarily being decentralized, right?
- 10:49SPEAKER_00: So um you I've seen this in in the space, right?
- 10:53SPEAKER_00: In in the traditional money movement space, right?
- 10:56SPEAKER_00: And and learning how it interacts with or doesn't interact with the like a blockchain rail, um, is that you you almost inevitably end up in a fiat space, right?
- 11:07SPEAKER_00: Uh like the on-off ramp piece.
- 11:09SPEAKER_00: Um, because the surrounding financial ecosystem, how you actually get your money is all traditional.
- 11:14SPEAKER_00: It's all traditional banking, it's money movement, right?
- 11:17SPEAKER_00: So while something may be decentralized in crypto, everything around it is not necessarily decentralized, right?
- 11:24SPEAKER_00: And but it by the time it it may be, I guess maybe this is the point, right?
- 11:28SPEAKER_00: By the time it gets to um the traditional level, uh you may it it may be kind of too far gone, right?
- 11:35SPEAKER_00: And that and that's I think the the lens that um you know for for years, ever since crypto has become a thing, that's been talked about, right?
- 11:43SPEAKER_00: Is it's you know, you you hear the point about it being anonymous and this and that and the other.
- 11:47SPEAKER_00: Um, you know, it's really not um, you know, when the the further you dig into it, it's really not completely, right?
- 11:53SPEAKER_00: There's a there's a trail.
- 11:54SPEAKER_00: Um but I think the point that does hold is that once it kind of leaves, you may not get it back, right?
- 12:02SPEAKER_00: If if it's if it's been sufficiently obfuscated, um it's difficult to to kind of reach out and grab it, um, depending on where the where the where the funds are, right?
- 12:11SPEAKER_00: So um just a really interesting case study here.
- 12:15SPEAKER_00: Um I think another point too, um just stablecoin issuers, exchanges, market makers, lending protocols, blockchain governance bodies, you know, and they all have different capabilities to intervene, right?
- 12:30SPEAKER_00: To that that last point.
- 12:32SPEAKER_00: Um those are those are it it depends on where it is, where it's gone, and where it's going to, um, as far as you know, if you're a if if you can even intervene and and and get the money back, um, which which creates you know a complicated international uh recovery process um just to bring that point home.
- 12:52SPEAKER_00: But I think just to bring it home, right, as far as the financial system implications, right?
- 12:58SPEAKER_00: So um, you know, this is not simply a story about cryptocurrency, um, as we've kind of talked about.
- 13:04SPEAKER_00: Um it's a it's a story about financial infrastructure risk.
- 13:08SPEAKER_00: Um and traditional financial institutions and crypto exchanges face different uh you know technical architectures.
- 13:14SPEAKER_00: Again, I'm not a technologist, but I know enough to know that there are different technical architectures.
- 13:19SPEAKER_00: Um and they and but there are several there they share several core challenges, right?
- 13:24SPEAKER_00: Protecting privileged access, securing employee devices, managing third-party software risk, preventing unauthorized transactions, monitoring abnormal movement of funds, coordinating incident response across institutions, uh, and maintaining customer confidence after a security event.
- 13:43SPEAKER_00: Right.
- 13:44SPEAKER_00: And the attack also demonstrates the importance of separating transaction authorization from transaction execution, right?
- 13:50SPEAKER_00: So that was the biggest piece that I learned as I dug into this, right?
- 13:54SPEAKER_00: Is oh wow, this wasn't simply a come in and just grab money, right?
- 14:00SPEAKER_00: It was a sophisticated attack that uh sort of tricked the system into thinking authorization had been obtained when it had it, right?
- 14:12SPEAKER_00: So that that was that was the piece I found really interesting.
- 14:16SPEAKER_00: Um and you may as well if you haven't read the Binance write up.
- 14:19SPEAKER_00: Um again, dated October 29th.
- 14:21SPEAKER_00: Um, it's really interesting.
- 14:23SPEAKER_00: Um, there's a lot of good thought leaders on the space, those that know a lot more about this than I do, um, kind of talking about it.
- 14:29SPEAKER_00: And I encourage you to go out there and and and kind of can consume what what's out there.
- 14:34SPEAKER_00: But as far as understanding it from a traditional financial infrastructure piece and risk mitigation, controls, compliance, um what could go wrong, right?
- 14:43SPEAKER_00: The the the folks who do that, it this was this was particularly interesting.
- 14:47SPEAKER_00: Um, and it's a really unique case study.
- 14:50SPEAKER_00: Um I'd love to know, I'd love to hear from you.
- 14:52SPEAKER_00: Um leave a comment, um, reach out.
- 14:55SPEAKER_00: Um what were some of your thoughts on it?
- 14:57SPEAKER_00: Are you maybe you're in the information security space?
- 15:00SPEAKER_00: Um, what would you elaborate on?
- 15:02SPEAKER_00: What what um what what are you doing now as a consequence of this?
- 15:07SPEAKER_00: Um, you know, to further strengthen your own infrastructure, um, or what are you counseling other teams to do?
- 15:12SPEAKER_00: Right.
- 15:13SPEAKER_00: I'd be very curious to hear from uh you know technologists um in the space um about you know what their thoughts were.
- 15:20SPEAKER_00: Um again, love to reach out to uh love to hear from you, reach out on on X, um, leave a comment on the podcast, uh, and until next time.