Has Coinbase dealt with similar data issues before?

Yes. In 2025 Coinbase disclosed that customer information had been obtained through bribed overseas support contractors and said it rejected a ransom demand tied to that incident. That episode, like this one, involved people or suppliers rather than the exchange's core trading and custody systems. It illustrates why vendor and contractor oversight is treated as part of an exchange's security posture.

Coinbase Denies Systems Breach, Says Vendor Amplitude Exposed Customer Contact Data

Q: Why does exposed contact data matter if no funds were taken?

Contact details are the raw material for convincing phishing campaigns that impersonate an exchange's support or security team. Crypto transfers are typically irreversible, so a successful scam can be costly for the victim. Leaked emails or phone numbers do not by themselves grant account access, but they make fraudulent messages appear far more legitimate.

Coinbase says an incident at analytics provider Amplitude exposed some customer contact details, but the exchange found no sign that its own systems were compromised. The disclosure highlights how much customer data flows through outside software vendors.

Disclaimer: News content is based on public news sources and provided for information only. It does not constitute investment advice.

Coinbase Denies Systems Breach, Says Vendor Amplitude Exposed Customer Contact Data

Cointelegraph·10/28/2026, 07:42:55· crypto

What Coinbase Said About the Incident

Coinbase stated that an incident at Amplitude, a third-party analytics vendor, resulted in the exposure of some customers' contact data. The exchange said it has found no evidence of unauthorized access to its own systems, effectively rejecting the framing of a Coinbase breach. The company's statement separates the event at the vendor from the security of its own infrastructure. Contact information — such as names, email addresses or phone numbers — is the category identified, rather than account credentials or balances.

Why a Vendor Incident Is Not the Same as an Exchange Breach

Analytics providers like Amplitude are typically embedded into consumer apps through software development kits that log how users move through a product. Those integrations can carry identifiers and, depending on configuration, customer contact details to the vendor's environment. When exposure occurs on the vendor side, the exchange's own servers and custody systems may remain untouched, even though customer data has left the building. That distinction matters legally and operationally: it changes which party must notify affected users and which systems require remediation. Coinbase's denial is therefore about the perimeter of its own infrastructure, not about whether data left its control.

Contact Data Is a Common Starting Point for Fraud

Exposed names, emails and phone numbers are frequently used to build convincing phishing messages that impersonate a brand's support team. Because crypto transactions are generally irreversible once confirmed, attackers often target exchange users with fake security alerts or fraudulent wallet-drainer links. A leaked email address alone does not give access to an account, but it can make a scam message far more credible to the recipient. This is why exchanges treat contact data exposure as a customer-protection issue even when passwords and funds are not involved.

Third-Party Risk Has Been a Recurring Theme for Coinbase

Coinbase, which trades on Nasdaq under the ticker COIN, has previously disclosed incidents in which customer information was obtained through people rather than through network intrusion. In 2025 the company acknowledged that bribed overseas support contractors had leaked account data, and it publicly rejected a ransom demand linked to that episode. Vendors and contractors sit outside the core security perimeter but often hold or can reach the same customer records, which makes their controls a live part of an exchange's risk profile. Regulators in the US and Europe have increasingly asked financial firms to document how they oversee such suppliers.

Coinbasedata breachthird-party riskcybersecuritycrypto exchange

Frequently asked questions

Did Coinbase itself get hacked?▾

Coinbase says it found no evidence of unauthorized access to its own systems, and attributes the exposure to an incident at analytics vendor Amplitude. The distinction is between an intrusion into the exchange's infrastructure and data held in a third-party tool. Because the event happened at the vendor, the affected data and notification responsibilities may differ from a direct breach.

What kind of data was exposed?▾

According to Coinbase, the exposed information involved some customers' contact data, a category that generally covers details such as names, email addresses or phone numbers. Contact data is different from credentials or account balances, which the statement did not say were affected. The company has not publicly detailed exactly which fields or how many customers are involved.

What is Amplitude and why would it hold customer data?▾

Amplitude is a product analytics company whose tools are built into apps to measure how users interact with features. Those integrations can transmit user identifiers and, depending on how they are configured, contact details to the vendor's platform. As a result, an incident at an analytics provider can expose customer information even when the app operator's own systems are not compromised.

Why does exposed contact data matter if no funds were taken?

Key takeaways

What Coinbase Said About the Incident

Why a Vendor Incident Is Not the Same as an Exchange Breach

Contact Data Is a Common Starting Point for Fraud

Third-Party Risk Has Been a Recurring Theme for Coinbase

What Disclosure Means for Affected Users

Common mistakes to avoid

Reacting to a single headline without reading the full context — one data point is rarely the whole story.
Treating rewritten news as a signal — it describes what happened, never what to do next.
Confusing AI-rewritten content with the original source — always verify important facts against the primary report.

Coinbase Denies Systems Breach, Says Vendor Amplitude Exposed Customer Contact Data

What Coinbase Said About the Incident

Why a Vendor Incident Is Not the Same as an Exchange Breach

Contact Data Is a Common Starting Point for Fraud

Third-Party Risk Has Been a Recurring Theme for Coinbase

Frequently asked questions

Key takeaways

Common mistakes to avoid

Related reading

What Coinbase Said About the Incident

Why a Vendor Incident Is Not the Same as an Exchange Breach

Contact Data Is a Common Starting Point for Fraud

Third-Party Risk Has Been a Recurring Theme for Coinbase

Frequently asked questions

Key takeaways

Common mistakes to avoid

Related reading

What Disclosure Means for Affected Users