Coinbase Says a Breach at Analytics Vendor Amplitude Exposed Some Customers' Contact Data
Coinbase denies it was breached and says customer funds are safe. It does confirm that an incident at Amplitude, its analytics provider, reached contact details for some of its customers. It hasn't said how many, and the 70,000-plus figure making the rounds on X has no official backing.
"Coinbase has not had a data breach," the company's support account posted on X late on Tuesday, October 27, US time [1]. Amplitude, it said, "experienced a security incident which impacted a small subset of Coinbase customer contact data, among other Amplitude customers." Coinbase reported no evidence of unauthorized access to its own systems, said customer funds were not impacted, and said it is notifying affected customers and regulators as the law requires [1].
The company has not said how many customers are affected, which contact fields were involved or when the incident happened [2]. Amplitude had not published a statement when this piece was written.
An unconfirmed number
Coinbase has confirmed neither that figure nor any other. Wu Blockchain noted as it relayed the claim that there was no official confirmation, and compared it with Coinbase's 2025 incident [5]. That was a different case, in which overseas support contractors accessed data on 69,461 customers, in some cases including ID images and account balances [6].
Phishing is the real risk
An email address or phone number won't open an account, but it tells a scammer exactly whom to target. As CoinDesk points out, exposed contact details are raw material for phishing and social engineering even when no passwords or keys leak [2]. Coinbase warned in September about callers posing as police who push victims to open an account and move funds to a "safe" wallet [7].
A few habits go a long way:
- Never share your seed phrase. Coinbase says it will never ask for seed phrases or two-factor codes, or tell you to move funds [8]. No legitimate service does.
- Ignore the links and numbers in the message. Open the app or type coinbase.com yourself. If someone calls, hang up and reach out on your own.
- Don't rely on the sender address alone. Coinbase advises checking that email comes from @coinbase.com [8], but this week we saw phishing sent from Foundation's real domain.
- Treat urgency and personal details as red flags. A message that knows your name or email isn't genuine because of it.
- Lock down the account. After the 2025 incident, Coinbase recommended turning on two-factor authentication and withdrawal allowlisting [6]. An authenticator app or hardware key doesn't depend on your phone number, the kind of data that may now be in the wrong hands.
Sources
Source type in parentheses. Web pages accessed on October 28, 2026.
- Coinbase Support (@CoinbaseSupport), statement on X, October 28, 2026. Amplitude incident, "small subset" of contact data, no access to Coinbase systems, funds not impacted. (Primary, official X account)
- Omkar Godbole, Coinbase says user funds are safe after vendor exposes customer data, CoinDesk, October 28, 2026. Unspecified count and fields, phishing risk. (Secondary, press)
- DelCrxpto (@DelCrxpto), post on X, October 28, 2026. First mention of more than 70,000 users. (Primary, unverified claim)
- 23pds (@im23pds), post on X, October 28, 2026, quoting source 3. (Primary, unverified claim)
- Wu Blockchain (@wublockchain12), post on X, October 28, 2026. No official confirmation of the figure and comparison with the 2025 incident. (Secondary, press)
- Sergiu Gatlan, Coinbase says recent data breach impacts 69,461 customers, BleepingComputer, May 21, 2025. Maine attorney general filing, exposed data and Coinbase's recommendations. (Secondary, press)
- Coinbase Support (@CoinbaseSupport), scam alert, September 30, 2026. Fake police pushing victims to move funds to a "safe" wallet. (Primary, official X account)
- Coinbase Support (@CoinbaseSupport), warning about fake emails, June 4, 2025. @coinbase.com sender and what the company never asks for. (Primary, official X account)
More in Privacy and self-custody
Last updated: October 29, 2026
