Ah, October. The month of ghouls, pumpkin lattes and the delicious taste of… hacks. Yum. With this I welcome you to another edition of Crypto: Decrypted and, while we had lots of great things to discuss this month, everything has simply been overshadowed by the largest crypto heist in history. I suppose it’s kind of like bobbing for apples. $6.3 billion apples. You can find all the facts online so for this missive I’d like to provide a little color, a little commentary and, I hope, some common-sense takeaways. Without further ado…
The Mother of All Hacks
What used to be universally known as “Uptober”, due to the general trend for the digital asset markets to run in this spooky month, is clearly in need of a rebrand after the past couple of years. Might I submit we consider the moniker, “Hacktober”? October 29, 2026 started seemingly like any other day, but by the afternoon social media started to post about a potential breach at the world’s largest digital asset exchange, Binance. Soon the worst fears were confirmed and in about 20 minutes $6.3B left Binance’s hot wallets. Like. A. Ghost.
And the weakness that was exploited? Humans.
This was not a blockchain weakness. This wasn’t autonomous AI. This wasn’t some new math or a fancy algorithm or quantum compromise. This was an old-fashioned hack via a compromised human. More specifically, it was an elaborate social engineering scheme that had been baking for months. It seems, back in June, an engineer at Binance inadvertently downloaded malware. Binance caught this but not before the hackers had a chance to figure out who else was on the team they could potentially exploit. In September, another engineer indeed was contacted under the ruse of a job interview. Through the interview process the hackers, posing as executives, were able to convince the engineer to download a “coding test” to his laptop. Of course, what was downloaded, was malware. The short story here is that this malware, using an internal AI (which Binance has not disclosed exactly which) was able to compromise their hot wallets on the Binance exchange. But I mean, c’mon guys. I’m paranoid about downloading anything to my laptop and I’m not an engineer at the largest digital asset exchange in the world. If you’re at Binance? Seriously. The first rule of no-hack club is we don’t download interview tools or tests. The second rule of no-hack club is we don’t download interview tools or tests.
So, yeah, this is awful, and one might expect the skies to completely fall and the markets to fall into a pit in Mordor. They didn’t. In the wake of this $6.3B (Six-point-three-BILLION dollar) hack bitcoin fell a whopping 4% in a day. 4%. I mean, that’s like normal volatility in these markets. As a bit of perspective, when a failed attack was attempted on Binance in March 2018 we had an 11% collapse in one day that degraded into 38% on the month. Nothing was stolen in 2018. Funds were safe. The platform was not compromised. Yet the markets cratered. I see this as really good news actually, and it shows how things have changed and how mature our markets really are. This hack was absorbed in stride and, as of this writing the markets held their ground. It could have been much worse. Indeed maybe it should have been much worse. But it wasn’t, which to me is an incredibly bullish sign indeed, showing how far we have come. A big part of which I attribute to institutional adoption and an overall crypto market cap of roughly $2.6T+.
I’m sure no small part of this is that Binance has publicly stated every loss will be covered, in part via their Secure Asset Fund for Users (SAFU) and the rest from Binance’s coffers. I’m sure it helps that Binance, through partners, was able to freeze on-chain assets totaling approximately $3B, which could be recovered lessening the amount that the company will need to come out of pocket. Former Binance CEO Changpeng Zhao (CZ) has been very public about the fact that there is no 100% security… but also that user funds would be covered.
The FBI has attributed this to North Korea’s TraderTraitor, the same group accused of the Bybit hack and a part of the North Korean Lazarus group. I’m not going to spend too much time here. I just want to emphasize that, yes, this hack was massive. And the antagonists are sophisticated. So we all need to be on our guard. To that end consider a few safety tips for all of us:
Don’t download anything unless you really need to. If you have to download something, do it from a verified site (like the app store), then verify it again. If you are in a dev shop, only use dev shop authorized downloads. For gosh sakes don’t download something to take a job interview.
If you’re contacted for a job that sounds too good to be true, it probably is. Even so don’t download anything to help the interview process. (See Rule 1.) This is a top social engineering scam that has absolutely gutted companies.
If you do have to do #1 and #2, and you work at a place such as, oh, say, Binance, for gosh sakes don’t do it on your work laptop.
Not relevant to this but a good habit: If you are ever prompted to enter your 12/18/24 word passphrase online… don’t. You only enter this when you are deliberately trying to restore a wallet, preferably on a cold wallet directly such as a Trezor that has been purchased from a manufacturer directly.
Due to the recent hardware wallet challenges (Coldcard, Ledger), consider using institutional grade cold storage. If nothing else, diversify the platforms upon which you hold your assets.
Don’t keep real assets on a hot exchange.
Use. Common. Sense.
I’ll vamp on the last for a moment. We all need to bring common sense and caution to everything we do in this changing digital age, because any lapse can cause a breach. You don’t need to be paranoid (well, maybe a little). You do need to be present. From my seat I think it’s just a matter of time before we see more and more challenges, and yes an exploit, in the world of traditional finance as well. I hope not. We’ll see.
Meanwhile…
While all this was going on, Wall Street just kept on wall-streeting. The day before the hack the Depository Trust Company (DTC) launched the DTCC Tokenization service, which brings tokenized securities into markets with the same ownership rights and protections as traditional counterparts. Participants included Bank of America, Citi, J.P. Morgan, Morgan Stanley, Fidelity, State Street, UBS and Citadel Securities. Not a bad crowd, from a Wall Street perspective. This could well be the beginning of the future of the financial markets.
At the same time, OKX raised capital at a $25B pre-money valuation, with Circle, Ripple, Standard Chartered's SC Ventures and QRT taking part. Not to be outdone Payward, parent of legendary crypto exchange Kraken, agreed on October 14 to buy Lithuania's Saldo Bank, which would make it the first crypto-native owner of a European bank. This is interesting because this transaction would allow deposits, loans, credit cards and euro transfers, a big contrast to US trust charters like Ripple's and Coinbase's, which do not.
And, last but not least, NYSE owner Intercontinental Exchange agreed to take a stake in Trade.xyz and build a regulated US market for 24/7 perpetual futures on Hyperliquid. This is pending regulatory approval of course, but creates the stage for a US presence and ability to use this blockchain which has taken the world by storm. Not surprisingly HYPE, Hyperliquid’s token, jumped 15% on the news. I like this because HYPE is one of the great crypto stories as it’s a product that is actually generating cashflow (the majority of which is used for buybacks) yet the perpetuals to which it provides access have not been available in the US… yet. This should change that.
All this in the same month that crypto, literally, got robbed. I guess there are two sides to every coin…
blockchAIn: AI plugs the hole
Before Hacktober occurred this blog probably would have been titled Black October because of the highly publicized PHP vulnerability which got all of the attention earlier in the month. For those that have been off-planet or who otherwise may have missed this, the world wide web went into a defensive posture to patch a bug that could potentially allow exploits to up to 70% of the world’s websites if not resolved. Ouch. The really interesting thing is that AI wasn’t the exploiter here. AI actually found the bug (which allowed the fix). This story reads like a Bond movie when one gets into it.
The PHP bug, known as “PHP2Shell” was actually a bug that had been hiding in PHP code for over a decade. OpenAI launched a program called “Patch the Planet” and this program, which involved researchers using AI, found the bug in August while Wiz, a cloud cybersecurity company following a similar path, also found the bug the same month. That was discovery. The reason we only heard about it in October is that PHP governs approximately 70% of the world’s websites. This means that, if the bug was revealed without a patch then, well, we’d really have Webmageddon. So, then, much like a crafty secret service agency, those who found the bug clued in key cybersecurity companies and internet giants specifically so that they could create some defensive walls. Simultaneously, the security team worked diligently to create a patch. What I find really amazing, and kind of inspiring, is that those that knew at OpenAI, Wiz, Cloudflare, AWS, and any other “in the know” kept everything on the down-low. That’s huge.
Now the plan was to have the patch complete and released on October 22nd but, remember that part about keeping it a secret? Oops. Someone “accidentally” leaked information on October 20th discussing the issue. (How someone could “accidentally” do this is beyond me so this is one of those plot holes we just have to live with.) Though taken down quickly, this rifled through the hacker community and showed up on Hacker News the same day, leading said hackers to start poking at PHP everywhere. This prompted an emergency scramble finalizing the patch and pushing it into markets on the 21st, creating the massive push to patch the world’s websites. whew.
So the real question is “what would have happened” should that bug have been leaked. Fearmongers assumed that AI would just run willy nilly over the world’s websites and create a meltdown, but that was just conjecture. In order to test this theory a gentleman named James Pavur launched the “Steal My Bitcoin” site, with a $2,000 bitcoin bounty awaiting those who could exploit the vulnerability. The question was, would AI just bore right in and get it. The answer was no. Fully autonomous bots did not break in. Ultimately, it was a human security researcher named “Killa” (you can’t make this stuff up) who cracked it. Did Killa use AI? Yes he did. Did the break require human ingenuity? Yes it did.
So, in summary: AI found a bug. Humans built a patch and kept mum for about 70 days. Humans then spilled the beans too early. A rushed patch was put into the marketplace. Websites were patched. There was much rejoicing. Then an open bounty demonstrated that humans still needed to be drivers of real carnage (Steal My Bitcoin). It also demonstrated that AI was a trusty sidekick in such exploits.
A very similar thing happened regarding an XRP bug that would have let an attacker create XRP “from nothing”. This bug was found in September via an AI agent, patched within days, then disclosed on October 9th. No mainnet funds appear to have been affected. AI-assisted researchers found it. The white hats fixed it. And there was much rejoicing.
What I like about these stories is that we live in a world where there’s a lot of negativity about how AI is going to wreck everything, where in this case AI allowed us to create a solution to a problem before it was exploited, and we see humans and AI working together for the greater good. Web2. Web3. Blockchain. Web whatever. AI can be a noble tool, if indeed used nobly. And that’s a comforting thought.
In Closing
I still love these markets and, personally, am excited for what is next. The biggest crypto hack in the world has turned out, for me anyway, to be a bullish sign. Prices held, and all losses were pledged to be covered. Our markets are maturing and demonstrating their resilience, which is very, very exciting. And, while that event took everyone’s attention, building kept happening and AI was, actually, used for technological good.
As we advance over the coming years I suspect there will be plenty of change. Humans are certainly a weakness as we saw in the Binance hack. But on the other side, humans using AI have actually mitigated problems that could have been devastating. Maybe we’re going to see human resilience lead the way into this new age where AI and humans collaborate. And that is, in my view, a very good thing, because the Blockchain/AI genie is simply not going back into the bottle.
That’s all for now! Until next time be well, take care, and I’ll keep Decrypting Crypto for you!