Key points
- Coinbase says an Amplitude incident exposed contact data for a small subset of customers.
- Coinbase has not disclosed the affected fields, customer count or incident date.
- The company says it found no unauthorized access to its systems and that customer funds were not affected.
- Verify alerts inside the official app or site and never surrender credentials, two-step codes or remote access.
The Coinbase Amplitude incident arrived with a familiar corporate distinction: Coinbase said it had not suffered a data breach. Its analytics vendor had.
For customers whose contact details crossed that boundary, the practical risk does not disappear with the wording. A convincing email, text or call needs no access to a crypto exchange’s vault. It only needs enough information to make the target hesitate.
On October 28, 2026, Coinbase Support disclosed that a security incident at Amplitude affected customer contact data belonging to a “small subset” of Coinbase users and other Amplitude customers. Coinbase said it found no evidence of unauthorized access to its own systems, that customer funds were not affected, and that it was notifying affected customers and regulators.
The Coinbase Amplitude incident therefore has a confirmed vendor-side exposure and an incomplete public scope. Those are Coinbase’s findings. They are not an independent forensic report, and the public statement leaves important questions unanswered.
What the Coinbase Amplitude incident confirms—and what it does not
The confirmed scope is narrow: customer contact data at a third-party analytics provider. Coinbase did not publicly identify the specific fields exposed, the number of affected users, the date of the incident, or the other Amplitude customers involved.
Independent reports from Cointelegraph and Decrypt found the same gap. Cointelegraph said Coinbase had not answered its request for an affected-customer count by publication. Decrypt reported that the company did not specify the types of contact data involved.
That means claims circulating about an exact victim count or particular exposed fields should not be treated as established from the available evidence.
Why contact data can still threaten crypto holders
A contact record is not a recovery phrase or a private key. The disclosed incident does not establish that attackers can sign transactions, reset accounts or move assets.
Contact data can, however, make social engineering more precise. A message that knows which service someone uses can imitate a security warning, withdrawal alert or support case. The objective is often to make the customer reveal credentials, approve remote access or authorize a transfer.
Coinbase’s own phishing guidance says official email comes from addresses ending in @coinbase.com. A separate security guide recommends a security key or passkey for two-step verification and warns that Coinbase Support will not request passwords, two-step verification codes or remote access to a computer.
What affected customers should do now
Do not act through a link, phone number or wallet address supplied in an unexpected message. Open Coinbase through a saved bookmark or the official app and check notifications there.
Use a passkey or hardware security key where available. Review active sessions, two-step verification settings, withdrawal addresses and recent activity. If a message claims urgent account danger, end the conversation and contact support through Coinbase’s own site.
Coinbase says it is notifying affected customers. A notification can confirm that someone is in the disclosed group; it does not make every later message about the incident genuine. Coinbase says suspicious communications can be forwarded to security@coinbase.com.
This is the same operational lesson seen after other hardware-wallet and exchange data incidents: the keys may remain safe while leaked context helps an attacker write a better lie. Panther’s earlier investigation into Keystone customer-address exposure explains why data retention and targeted phishing deserve separate scrutiny from wallet-key security.
What evidence should come next
A useful follow-up should identify the affected data fields, the exposure window, how the incident occurred, how many Coinbase customers were involved, and what Amplitude changed afterward. Customers also need a clear way to verify notifications without trusting the notification itself.
Until those facts are public, two conclusions can coexist: Coinbase says it found no unauthorized access to its systems or customer funds, and customer contact data still escaped through a vendor. The first claim limits the known technical scope. The second creates a real human attack surface.
The Panther takeaway
The vault does not have to open for danger to move closer. Treat unexpected Coinbase contact as untrusted, verify inside the official app or site, and never surrender credentials, two-step codes, remote access or crypto to “secure” an account.
Sources and verification
- Coinbase Support, October 28, 2026 — primary disclosure of the Amplitude incident, stated scope and company findings.
- Cointelegraph, October 28, 2026 — independent report and confirmation that an affected-customer count was not provided by publication.
- Decrypt, October 28, 2026 — independent report noting that the exposed contact fields and incident date were not disclosed.
- Coinbase Help: phishing and account security — official defensive guidance.
Responses
No responses yet. Start the conversation.
Panther Journal — The intelligence brief
Stay ahead of the story.
Free. New investigations delivered when published. Unsubscribe anytime.






