Most people who swap tokens on Base did not get their ETH or USDC out of thin air. At some point they bought it on a centralized exchange, then sent it to a self-custody wallet before bridging it to Base. That exchange account, with its email, government ID and linked bank details, is a separate attack surface from your wallet, and it is one that occasionally gets breached. Understanding what a breach can and cannot expose helps you react correctly instead of panicking or, worse, ignoring it.
What a self-custody wallet protects, and what it does not
A self-custody wallet like the ones used to swap on Base stores your private keys locally, derived from a recovery phrase that never touches a company's servers. No exchange breach can hand an attacker your private key, because the exchange never had it. If your funds are in a wallet you control and your recovery phrase is offline, a breach at an exchange you used months ago cannot drain that wallet directly.
What self-custody does not protect is everything you handed over during account verification. Centralized exchanges are required to run identity checks, so they typically hold your full legal name, home address, date of birth, a photo of your government ID, and often bank account or card details. None of that lives on the blockchain, and none of it is protected by your seed phrase. It sits in a company database, and company databases get breached.
A real example worth knowing about
In 2025, Coinbase disclosed that a group of overseas customer support contractors had been paid by outside criminals to copy customer data from internal support tools. The exposed information included names, contact details, partially masked identification numbers, images of government IDs, and account activity history. Coinbase was clear that no passwords, private keys or customer funds were accessed, and that the affected accounts were a small fraction of its user base. The company fired the implicated staff and offered a reward for information leading to the attackers' arrest.
The incident is a useful case study because it shows the actual shape of exchange breaches. Attackers rarely find a clever way to bypass a private key. It is far easier to bribe or trick a human with database access, since personal information is valuable on its own for follow-on scams.
Why stolen identity data still matters to a self-custody user
Even if an attacker cannot touch your wallet, they can use your name, phone number and the fact that you own crypto to run a convincing scam. Breach data typically feeds three follow-up attack patterns:
Targeted phishing and fake support calls. An attacker who knows your real name, the exchange you use and your account activity can call or message you pretending to be support staff, referencing real details to sound legitimate. This is the same pattern covered in fake support and impersonation scams. No real exchange or wallet support team will ever ask for your recovery phrase.
SIM swap attempts. If a phone number was part of the leaked data, it becomes a target for a SIM swap, where an attacker convinces your mobile carrier to port your number to their device so they can intercept SMS codes. See SIM swap attacks and your crypto accounts for how that unfolds and how to make it harder.
Physical and financial targeting. A leaked home address tied to a known crypto holder is not a theoretical risk. It has been used in extortion and even in-person theft attempts against people publicly known to hold significant crypto. This is also a reason to keep your holdings and your identity as separate as reasonably possible.
What to actually do if you are notified
If an exchange tells you your data was part of a breach, a few concrete steps matter more than general anxiety:
- Assume your name, email and phone are now circulating. Treat any unexpected call, text or email referencing your exchange account as hostile until proven otherwise, even if it includes real details about you.
- Move to app-based or hardware two-factor authentication instead of SMS codes, since SMS is the weak link a SIM swap exploits. See two factor authentication for crypto accounts explained.
- Never act on urgency. Breach-fueled scams work by creating a sense that your account is about to be locked or drained right now. A support agent, real or fake, asking you to move funds immediately is a red flag on its own.
- Check your wallet's approvals if you ever connected it to apps around the same time as the exchange you used, since unrelated incidents sometimes cluster. A quick review is covered in how to check and revoke token approvals.
- Consider a fresh wallet for new activity if you are especially concerned, moving funds over with a direct, verified transaction rather than clicking any link sent to you after the breach announcement.
The bottom line
A breach at an exchange is not a breach of your Base wallet, and your recovery phrase stays exactly as safe as it was before. But the personal information exposed in these incidents is routinely weaponized against the exact audience reading this: people who are known, provably, to hold crypto. Self-custody protects your keys. It does not protect your inbox, your phone number or your government ID photo, so the habits that matter after a breach are the same ones that matter every day: verify independently, never share a recovery phrase with anyone, and treat urgency as a warning sign rather than a reason to act fast.
Sources: Coinbase insider bribery breach coverage, The Hacker News, TechRadar Pro report on the Coinbase breach.