Coinbase says user funds are safe after third-party vendor exposes customer contact info

20Importance
closedStatus
14News media
Published
Updated

Coinbase said a security incident at analytics provider Amplitude exposed contact information for a small subset of its customers, while its own systems showed no unauthorized access. The exchange said customer funds were unaffected and that it is notifying affected users and regulators.

Key claims & sources

✓
Coinbase said customer funds were unaffected by the incident and remain safe.
✓
Coinbase said it is notifying affected users and regulators.
✓
Coinbase said it found no evidence of unauthorized access to its own systems after the Amplitude incident.
✓
Coinbase said other Amplitude clients were also affected by the security incident.
✓
Coinbase said the disclosure came a day before it was scheduled to report third-quarter earnings.
✓
Coinbase said a security incident at analytics provider Amplitude exposed contact information for a small subset of its customers.

What it means

Coinbase runs its own custody and trading infrastructure but, like most consumer apps, outsources functions such as product analytics to outside vendors; Amplitude is one of many firms in that category, not a Coinbase subsidiary. The exchange has been here before: a 2025 incident involving bribed overseas support contractors leaked account data and fed phishing campaigns against its users, forcing Coinbase to separate 'systems breach' from 'data exposure' in its public language ever since. This week's statement follows that same script.

Affected customers gain nothing new to do with their holdings, since trading and withdrawal functions were never touched, but they do face a fresh phishing risk now that names, emails or phone numbers tied to their accounts may be circulating outside Coinbase's own systems. The practical response is to verify any contact through bookmarked official channels rather than links in unexpected messages, not to change passwords or move funds. Other Amplitude clients beyond Coinbase were also hit, spreading exposure, and scrutiny, across the vendor's whole customer base rather than one exchange.

The episode reframes crypto security as a supply-chain problem rather than a private-key problem: an exchange can harden its custody architecture and still leak customer data through a marketing-analytics tool it barely controls. That cuts against the self-custody pitch crypto has long made to new users, since the weak point here was never a wallet or a seed phrase but ordinary SaaS plumbing shared with companies outside the industry entirely. Coinbase's insistence that funds are safe is accurate but narrower than the trust question the incident actually raises.

Coinbase's statement landed a day before its third-quarter earnings call, which will be the first forum where executives face direct questions on the incident's scale, remediation costs and any regulatory notifications already filed. Watch for whether the company discloses a customer count there, since outside estimates, including a claim of more than 70,000 affected users from blockchain security researcher SlowMist, remain unconfirmed against Coinbase's own 'small subset' description.

Market reaction i

Total crypto marketall crypto assets combined no single asset in the event: read against the whole market

The total crypto market barely moved in the 4 hours after the first headline, after rising 0.1% in the 2 hours before.

$2.7T market cap at the headline
+0.1% 2 h before
0.0% 4 h after
-0.2% 12 h after
First headline

46 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

+5 min
Oct 28 03:16
The Defiant echo
No new facts: defiant, story, cites; with quotes
+49 min
Oct 28 03:59
Crypto Briefing context
Its angle: vulnerability, emphasizing, highlights
+4 h 32 m
Oct 28 07:42
Cointelegraph echo
No new facts: with quotes
+5 h 39 m
Oct 28 08:50
CR Cryptopolitan echo
No new facts: depicted, informat, touched; with quotes
+6 h 5 m
Oct 28 09:15
Unchained echo
No new facts: circulated, according, delcrxpto; with quotes
+6 h 59 m
Oct 28 10:10
+6 h 59 m
Oct 28 10:10
U.Today echo
No new facts: concerns, responds, recent
+8 h 1 m
Oct 28 11:12
Cryptonews.com context
Its angle: reimbursement, opportunities, verification; with quotes
+8 h 46 m
Oct 28 11:56
BeInCrypto echo
No new facts: beincrypto, anonymous, attackers; with quotes
+9 h 50 m
Oct 28 13:00
The Cryptocurrency Post echo
No new facts: transaction, businesses, passwords; with quotes
+10 h 7 m
Oct 28 13:18
CP CryptoPotato echo
No new facts: obligations, reportedly, accordance; with quotes
+10 h 50 m
Oct 28 14:00
Crypto Economy echo
No new facts: compromise, reviewing, platform; with quotes
+2 d 4 h
Oct 30 08:00
NewsBTC echo
No new facts: comprehensive, impersonation, notification; with quotes

Other recent incidents

WhenWhat happenedFigure
2 days ago B18 TimeBank · Unknown incident $404.5k
3 days ago MORE Markets · Unknown incident $308k
3 days ago Lighter incident $10.4M
3 days ago Optimizely (OPTIMJACK) · Supply Chain Attack incident $2.3k
4 days ago Luxor Commander · Unknown incident no figure in dollars

4332 incidents stored