Coinbase Confirms Vendor Breach as 3 South Korean Firms Report Separate Data Leaks
Amplitude breach exposed contact data for a small subset of Coinbase users, risking potential phishing attacks on investors.
South Korean firms disclosed breaches affecting up to 38,490 clients, prompting regulatory emergency response and market confidence concerns.
CZ urged stronger account security to prevent phishing and SIM‑swap fraud, highlighting possible financial losses from compromised credentials.
A post on X from an account posting under the handle 23pds, CISO at blockchain security firm SlowMist, claimed on Oct. 28 that a Coinbase data breach was “confirmed” and that hackers had obtained contact information for “over 70,000 users,” while adding that password or funds theft was “not yet confirmed.”
Coinbase Support responded directly on X the same day: “Coinbase has not had a data breach. Amplitude, an analytics vendor, experienced a security incident which impacted a small subset of Coinbase customer contact data, among other Amplitude customers. We’ve found no evidence of unauthorized access to Coinbase systems, and customer funds were not impacted.” Coinbase said it is notifying impacted customers and regulatory agencies in accordance with its legal obligations.
Coinbase did not confirm a specific number of affected users, and the “70,000” figure in the 23pds post doesn’t match Coinbase’s own “small subset” characterization of this week’s Amplitude incident.
Three South Korean Financial Firms Report Separate Breaches
The same week, three unrelated South Korean financial firms disclosed their own data breaches, according to Yonhap News.
Daishin Securities confirmed the clearest figures so far. The Korea Herald reports the brokerage disclosed that hackers accessed personal information belonging to 38,490 clients—names, email addresses, and mobile phone numbers—along with “key credit records.” Daishin says it detected signs of unauthorized access the previous week, has notified affected customers, and says it will compensate them under the law if the breach causes damage.
Bithumb, South Korea’s second-largest crypto exchange, detected abnormal traffic on Oct. 27. Attackers reportedly accessed its internal mobile-office collaboration system and took some internal data; Bithumb says it is still checking whether customer trading data was exposed, and no affected-user count has been disclosed.
Mirae Asset Global Investments, the asset-management arm of the Mirae Asset group (distinct from its brokerage, Mirae Asset Securities), was confirmed to have been breached as well, though neither the scope of the data accessed nor the number of affected clients has been reported yet.
South Korea’s Financial Supervisory Service (FSS) activated its highest-level emergency response and formed a joint investigation team, sending inspectors to Daishin’s offices and launching an industry-wide security sweep across financial firms, brokerages, and licensed virtual asset service providers, per TechFlowPost’s reporting.
CZ’s Response: You Can’t Prevent a Leak, But You Can Limit the Damage
Responding to the reports, Binance founder Changpeng Zhao (CZ) posted a detailed breakdown of account-security steps on X, opening with the point that leaked exchange data—names, emails, phone numbers, addresses, ID documents, and transaction history—is mostly weaponized for phishing, SIM swapping, and social engineering, not direct theft.
His recommendations fell into a few groups:
- Reduce what you share: Use a unique email alias per exchange (via services like SimpleLogin or Apple Hide My Email) so a leak can be traced to its source and not linked across accounts; skip optional profile fields; and use a dedicated phone number for exchange accounts where possible, since leaked numbers are the main route into SIM-swap attacks.
- Lock down the account itself: Unique, long passwords from a password manager; hardware security keys or passkeys over SMS-based two-factor authentication; withdrawal address whitelisting and time locks where offered; an anti-phishing code that appears in every legitimate email from the exchange; and regular review of active sessions and API keys, restricting any API key to withdraw-disabled and IP-whitelisted access.
- Defend against follow-on attacks: Add a port-out PIN or number lock with your mobile carrier against SIM swapping; treat anyone contacting you about “security issues” or account recovery as a scammer by default, even if they know personal details; and remember that exchange support staff never ask for passwords, 2FA codes, or seed phrases.
- If a breach affecting you is announced: Change the exchange password and any other account that reused it, check haveibeenpwned.com for your email, revoke API keys and active sessions, review recent withdrawals and security settings, and watch for breach-themed phishing attempts in the days that follow.
CZ also flagged “wrench attacks”—real-world extortion or robbery enabled by combining leaked addresses with visible holdings data—as a reason not to publicize crypto balances or keep large holdings tied to a home address where avoidable.
Past Context: CZ’s Other Recent Warning, Over a Critical PHP Flaw
This isn’t the first time this month CZ has told users to be cautious online. On Oct. 22, 2026, he warned, “Call me paranoid, but be extra careful visiting ANY web site in the next few days,” after developers rushed out emergency patches for two critical PHP vulnerabilities dubbed PHP2Shell: CVE-2026-109618 and CVE-2026-109619, each rated 9.2 out of 10 in severity.
According to a report, both flaws allow unauthenticated remote code execution on unpatched servers through use-after-free memory errors reachable via standard multipart/form-data requests—the kind used in ordinary login forms, file uploads, and payment portals. The risk sat specifically in the web layer: exchange dashboards, KYC portals, and wallet-connect pages built on PHP, rather than smart contracts or cold wallets.
Security researcher Ryan Austin discovered the first bug in August 2026, with Wiz Research and OpenAI reporting additional findings later; emergency patches for PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12 shipped Oct. 21, though exploitation attempts were reportedly already underway before the official fix. Several firms, including BNB Chain and Trust Wallet, said their stacks don’t use PHP at all, while Kraken noted it had already migrated its backend to Rust in 2025—leaving smaller exchanges running unpatched PHP portals as the most exposed.
That episode and this week’s run of breaches point to the same underlying lesson CZ’s latest advice is built around: the weakest point in exchange security is often not the blockchain itself, but the ordinary web infrastructure—vendors, login portals, internal collaboration tools—sitting around it.
Also Read: Solflare Pauses SOL Staking Rewards After Security Incident
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


