Third-Party RiskCrypto

Twenty Minutes, $6.3 Billion: What Binance Means for Partner Vetting

Attackers drained about $6.3 billion from Binance in minutes. Here is what that should change in how banks vet and monitor crypto-facing fintech partners.

Gaurav Raj Shrestha
November 17, 2026 · 4 min read
Abstract illustration of crypto wallets and a security lock representing partner due diligence

On October 29, attackers emptied Binance hot wallets across multiple blockchains. Most of the money left in about twenty minutes. Binance puts the loss at roughly $6.3 billion. Elliptic's count is a bit higher, and the figures are still moving, so treat every number in this post as provisional.

Two days later the FBI, with the Secret Service and IRS Criminal Investigation, attributed the theft to TraderTraitor, North Korea's state-backed group, and published a list of attacker-controlled addresses. Press coverage of the alert puts the list at 608 Ethereum addresses, 19 Bitcoin addresses and one Solana address.

You probably don't bank Binance. That's not the point. If you have an exchange, wallet, stablecoin or payments fintech in your program, you have a partner that touches the same rails, the same counterparties and the same launderers. The question for your next committee meeting is what you'd be able to show an examiner about how that partner protects customer assets, and how you'd find out if its funds were touched.

The first problem is custody, and most diligence files barely cover it

Standard fintech onboarding asks about policies, licenses, ownership and AML controls. Key management usually gets a line, if that. For a crypto-facing partner it deserves its own section.

Ask how private keys are generated, stored and used. Ask how much value sits in hot wallets at any moment, and what rule sets that ceiling. Ask who can authorize a large transfer, whether it takes more than one person, and whether any of those approvals can be automated or changed by one engineer's credentials. A partner that can't answer these in writing is telling you something.

Then ask about the thing nobody asks: what happened the last time something went wrong? Not whether they've had an incident, but how they handled it, who they told and how fast.

Incident notification terms are a contract question

If a partner is breached on a Tuesday night, when do you hear? Many agreements say "promptly" and nothing else. That's not a term, it's a hope.

Write in a specific window, measured in hours, for notice of any event that affects customer funds, keys or systems connected to your program. Define what counts. Require the partner to tell you what it knows, not what it has decided is safe to share. And make sure the agreement lets you see the partner's own post-incident review. When regulators ask what you knew and when, your answer is only as good as your contract.

Listed addresses are now a screening problem

Here's where it gets practical. The FBI list is not a sanctions list, but the people behind it are tied to a sanctioned state. Treat any link to those addresses as a potential sanctions exposure and a likely suspicious activity indicator, and escalate on that basis.

Two things to check this week:

  • Whether your partner screens inbound and outbound crypto flows against the published addresses, and how fast new additions get loaded. The Bybit alert in 2025 followed the same pattern, and the list grew afterward.
  • Whether your own monitoring can see through the partner. If you only see the partner's omnibus account moving dollars, you won't see a customer who received funds from a listed wallet. You'll need partner-level reporting on flagged exposure, not just a representation that screening exists.

One caution. The press accounts of the FBI alert describe requests aimed at crypto services, node operators and analytics firms. I haven't seen a statement that banks themselves are named recipients. Read the alert directly before you cite it in a policy, and don't assume it creates a duty for your institution.

Freezes help, and they don't solve it

Tether and Circle both froze large amounts of stablecoin within hours. Reported totals differ, and the figures come mostly from the issuers' own statements. On November 12 the Justice Department said it had court authorization to seize or restrain more than $1.2 billion of the roughly $2.7 billion frozen by government and private parties. That's authorization, not money in hand.

The lesson for compliance teams is the part that was not frozen. Bitcoin and Ether can move, and the FBI says TraderTraitor has been converting mostly into Ether, with further laundering expected through DeFi and instant swap services. If your partner offers swaps or off-ramps, those are exactly the doors stolen funds try next.

What an examiner will want to see

Not a perfect outcome. A record. At minimum:

  • A custody and security review in the partner's file, with dates and named reviewers.
  • Contract language on incident notice, audit rights and cooperation.
  • Evidence that listed-address screening exists, who owns it and how updates are loaded.
  • A note on what you did after the FBI alert: who looked, what you checked, what you found.

That last one is the item most programs lack. An alert comes out, everyone reads it, and nothing gets written down. The tools matter less than the habit. When the next alert lands, you want to be the institution that can show what it checked.

Note: this post reflects press reports and public statements as of mid-November 2026. Loss and freeze figures are provisional and sources differ. Review the primary FBI and Justice Department materials before relying on any specific number.

Keep reading
See it live

See how Across delivers decision-ready risk assessments.

Designed to empower your compliance team and keep you exam-ready at every stage.