Blog/Engineering
Engineering

Coinbase Data Breach via Amplitude: What Leaked, What Didn’t, and the Analytics SDK Checklist for Gulf and Egypt Apps

i
iFynx StudioOct 28, 2026 · 15 min read
The Dubai Internet City entrance sign in Arabic and English, home to many of the Gulf's app, fintech and analytics teams

Short answer: The Coinbase data breach reported on 28 October 2026 was not a break-in at Coinbase. Coinbase says its analytics vendor Amplitude had a security incident that exposed a small subset of Coinbase customers’ contact data (emails and phone numbers), along with data from other Amplitude customers. Coinbase says it found no unauthorized access to its own systems and that funds, passwords and private keys were not affected. Expect targeted phishing, and if you build apps in the Gulf or Egypt, stop sending personal data to analytics tools you don’t need to.

The Coinbase data breach headlines that spread overnight are really a story about the analytics code inside almost every modern app. In the early hours of 28 October, posts on X, repeated by a SlowMist executive, claimed contact data for more than 70,000 Coinbase users had leaked. Coinbase answered within hours: its own systems were not breached, and the exposure came from Amplitude, a product analytics vendor used by thousands of companies. This guide separates what is confirmed from what is claimed, explains what Coinbase users in the UAE, Saudi Arabia and Egypt should do now, and gives product and engineering teams a practical checklist for analytics SDKs, the third-party code that quietly collects user data in banking, fintech, e-commerce and government apps across the region.

Key facts (as of 28 October 2026, 09:00 Asia/Gaza)

  • 28 Oct, 02:49 UTC: Coinbase Support statement: “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” (Coinbase Support on X).
  • Exposed (per Coinbase and coverage): contact data, meaning email addresses and phone numbers (CoinDesk, Crypto Briefing).
  • Not exposed (per Coinbase): customer funds, passwords and private keys; no evidence of unauthorized access to Coinbase systems.
  • Number affected: not disclosed by Coinbase. An X account claimed “+70,000” users at 00:01 UTC and SlowMist’s CISO (23pds) repeated the figure at 02:17 UTC (23pds on X). Treat it as an unconfirmed claim.
  • Notifications: Coinbase says it is notifying affected customers and regulators in line with its legal obligations (India Today).
  • Amplitude: no public incident notice on its status page or Trust Center when we checked on 28 October.
  • Gulf link: Coinbase received an ADGM FSRA Financial Services Permission in August 2026 for its tokenization hub in Abu Dhabi (Coinbase).

What happened in the Coinbase data breach?

The timeline is short. Posts claiming a Coinbase leak started appearing on X late on 27 October (UTC); at 00:01 UTC on 28 October one widely shared account claimed hackers had contact details for more than 70,000 users. At 02:17 UTC SlowMist’s chief information security officer, known as 23pds, repeated that the leak was “confirmed”, while saying it was not yet clear whether passwords or funds were involved. At 02:49 UTC, Coinbase Support published its statement and then replied to many worried users with the same text. CoinDesk and Crypto Briefing reported the story shortly afterwards.

Coinbase’s position rests on a distinction that matters for engineers and regulators: its own systems were not accessed. The data left through a vendor. For users, though, the distinction changes little. If your email address and phone number are now in someone else’s hands, you will get more convincing scam calls and messages, whoever lost the data. Coverage of the incident has flagged exactly that phishing risk.

Two things are still unknown at the time of writing: how the attacker got into Amplitude data (a platform flaw, a stolen employee credential, or a compromised customer project key), and how many other Amplitude customers are affected. Coinbase’s phrase “among other Amplitude customers” means this is unlikely to stay a crypto-only story.

What data was exposed, and what was not?

Data typeStatusSource
Email addressesExposed for a small subset of customersCoinbase statement; CoinDesk
Phone numbersExposed for a small subset of customersCoinbase statement; CoinDesk
Number of affected usersNot disclosed; “more than 70,000” claimed on X and repeated by SlowMist’s CISOPosts on X
Passwords, private keysNot compromised, per CoinbaseCoinbase Support
Customer fundsNot affected, per CoinbaseCoinbase Support
Coinbase internal systemsNo evidence of unauthorized access, per CoinbaseCoinbase Support

This is very different from Coinbase’s May 2025 incident, when criminals bribed overseas support agents to copy customer records including government ID images. This time the exposed fields are narrower, but the attack path is one many companies have not mapped: a vendor that receives personal data from inside the app.

Is Coinbase hacked? Are my funds safe?

On the evidence published so far, Coinbase’s wallets and exchange systems were not breached and funds were not touched. Your account is not at risk because of this incident alone. It is at risk if a scammer uses your leaked contact details to talk you into handing over a code, approving a login or moving funds to a “safe wallet”. That is the classic follow-up to contact-data leaks, and it is the scam pattern Gulf police forces warn about most often. We covered the government and bank impersonation version in our guide to UAE online fraud.

What should Coinbase users in the UAE, Saudi Arabia and Egypt do now?

  1. Ignore unsolicited contact. Coinbase will not call you to move funds, ask for your 2FA code or send you a “recovery wallet”. Hang up and open the official app yourself.
  2. Check for the official notice inside your account rather than trusting an email link. Phishing emails will copy Coinbase’s notice word for word.
  3. Upgrade your second factor to a passkey or hardware security key instead of SMS, since your phone number may now be known.
  4. Watch for Arabic-language scams that cite “the Coinbase leak” and pose as Coinbase, a regulator or a bank fraud team.
  5. Report attempts: in the UAE through the eCrime platform or 901, in Saudi Arabia through the Kollona Amn app, and in Egypt through your bank and the Ministry of Interior’s cybercrime channels.

Why does an analytics vendor hold emails and phone numbers at all?

Product analytics tools such as Amplitude, Mixpanel and others work by receiving events from your app: screen viewed, button tapped, onboarding step completed. To join events into journeys they need a user ID. The problem starts when teams send more than an ID. A one-line identify() call that attaches email, phone, full_name or country_id as user properties copies personal data into a second database, run by a different company, often hosted in another country. Session replay tools can go further and capture what users type unless text fields are masked.

Analytics vendors keep turning up in incidents. In September 2026 the parking app SpotAngels said an unauthorized party used compromised credentials for its own Amplitude project to export user data, and stressed that Amplitude’s platform itself was not breached (SpotAngels). In November 2025, OpenAI disclosed that a breach at Mixpanel exposed limited profile data of some API users. The lesson is the same each time: whatever you send to an analytics vendor can leak from the vendor, or from your account at the vendor.

For apps in the Gulf and Egypt this carries extra weight. Banking, wallet, remittance and government-adjacent apps here often collect national ID numbers, Emirates ID or Iqama details, IBANs and verified phone numbers through eKYC flows such as UAE Pass and Nafath. One careless analytics property can push those fields to a vendor that never needed them.

The analytics SDK checklist for Gulf and Egypt apps

This is the checklist we use when we audit analytics in client apps. Most items take hours, not weeks.

  1. Inventory every SDK. List all analytics, attribution, crash, session-replay and marketing SDKs in your iOS, Android and web builds, and which events and user properties each receives. Generate it from code, not from memory.
  2. Send IDs, not identities. Replace email, phone, name, national ID, IBAN and card fragments with a random internal user ID. If you must link records, hash with a secret salt held on your server.
  3. Block PII at a proxy. Route events through a server-side collector or CDP with a strict field allowlist, so a developer’s stray identify({email}) is dropped before it leaves your infrastructure.
  4. Mask session replay by default. Mask all text inputs, including Arabic RTL fields, OTP boxes, amounts and beneficiary names. Exclude KYC, payment and card screens entirely.
  5. Lock down the vendor console. SSO, enforced MFA, named accounts only, quarterly access reviews, and the fewest possible people allowed to export raw data or create API keys.
  6. Rotate and scope keys. Treat analytics secret keys and export API keys like production credentials: keep them in a vault, rotate them after staff changes and after any vendor incident (today is a good day), and never ship secret keys in mobile apps.
  7. Set short retention. Behaviour analytics rarely needs raw user-level data older than 12 to 18 months. Use the vendor’s deletion API to honour deletion requests.
  8. Choose the data region deliberately. Many analytics vendors offer only US or EU hosting. Document that choice as a cross-border transfer for Saudi PDPL, UAE PDPL and Egypt’s PDPL purposes.
  9. Contract for incidents. Your data processing agreement should require the vendor to notify you within 24 to 48 hours of a suspected incident, share affected fields and customer counts, and support your regulator notifications.
  10. Rehearse the user notice. Prepare bilingual Arabic and English notice templates, an in-app banner and a support script now, before you need them.
FieldSend to analytics?Safer alternative
Email, phone numberNoInternal random user ID
Full nameNoNothing; analytics rarely needs it
Emirates ID, Iqama, Egyptian national IDNeverBoolean such as kyc_verified
IBAN, card digits, wallet addressNeverBank or card type, never the number
City or emirateUsually fineCoarse region, not GPS coordinates
Transaction amountOnly if neededBucketed ranges, for example 0-500 AED
App language (ar/en), RTL modeYesUseful for Arabic UX analysis

What do UAE, Saudi and Egyptian rules require if a vendor leaks your customers’ data?

Using a vendor does not move responsibility away from you. Under the region’s data protection laws the company that decided to collect the data, the controller, remains accountable for its processors. In brief, and not as legal advice:

  • Saudi Arabia: under the PDPL and its Implementing Regulation, controllers must notify SDAIA within 72 hours of becoming aware of a breach that may harm data subjects, and inform affected people without undue delay where there is harm. Sending data to a US-hosted vendor is also a transfer outside the Kingdom. (Our Saudi PDPL compliance guide covers the detail.)
  • UAE (federal): Federal Decree-Law No. 45 of 2021 requires controllers to notify the UAE Data Office of breaches that affect the privacy, confidentiality or security of personal data, and to inform data subjects in specified cases. Processors must tell the controller.
  • DIFC and ADGM: both free zones have their own data protection regimes with breach notification to their Commissioners; firms licensed there, including crypto and fintech firms, follow those rules.
  • Egypt: the Personal Data Protection Law No. 151 of 2020 requires controllers and processors to notify the Personal Data Protection Center within 72 hours of a breach.
  • Financial regulators such as the CBUAE, SAMA, VARA, the DFSA, the FSRA and the Central Bank of Egypt may expect separate incident reports from licensed firms.

The practical takeaway: you can only meet a 72-hour clock if your vendor tells you quickly and you already know which personal fields you send them. That is why the inventory in step 1 matters more than any other item.

How should an app tell users about a vendor incident?

Coinbase’s first public line, “Coinbase has not had a data breach”, was accurate about its systems but landed badly with users whose data had leaked. A better pattern for Gulf apps is to lead with what happened to the user: “Your email and phone number may have been exposed through one of our service providers. Your money and password are safe.” Then say what you are doing, what the user should do, and how to tell a real message from a fake one. Put the notice inside the app, where scammers cannot copy it, and keep Arabic and English versions equally complete. If your app has a scam-warning layer, switch it on for the next few weeks: show an interstitial before transfers to new beneficiaries that says “We will never call you to move your money.”

How iFynx audits analytics in client apps

At iFynx (آيفينيكس) we build and maintain mobile and web apps for clients in the UAE, Saudi Arabia and Egypt, and an analytics audit is one of the fastest privacy wins we deliver. We pull the SDK list from the build files, run the app through a proxy to capture every outbound analytics payload, flag any field that looks like an email, phone, ID or IBAN, and fix the source with an allowlisted event schema. The same review usually turns up forgotten SDKs from old campaigns. If you also run web properties on PHP or Node.js, this week’s PHP2Shell and Brotli vulnerability checklists are worth doing in the same sprint.

Crypto and trading apps deserve extra care. The UAE now has a busy licensed market, from Standard Chartered’s crypto trading for UAE clients to Robinhood’s DFSA authorisation. For those apps, a leaked phone number is a ready-made target list for impersonation scams.

Frequently asked questions

Was Coinbase hacked?

Coinbase says no. In its statement of 28 October 2026 the company said it found no evidence of unauthorized access to Coinbase systems and that customer funds were not affected. The exposure happened at Amplitude, a third-party analytics vendor, and touched a small subset of Coinbase customer contact data along with data of other Amplitude customers. For the people whose emails and phone numbers leaked, the practical risk is the same as a breach: targeted phishing.

What data was exposed in the Coinbase Amplitude incident?

According to Coinbase and the coverage so far, contact details: email addresses and phone numbers. Coinbase says passwords, private keys and funds were not compromised. Posts on X, repeated by security firm SlowMist’s CISO, claimed more than 70,000 users were affected; Coinbase has not confirmed a number. Amplitude had not published its own incident notice when we checked on 28 October.

Are Coinbase users in the UAE, Saudi Arabia or Egypt affected?

Coinbase has not broken the affected group down by country. It says it is notifying affected customers and regulators as the law requires. If you hold a Coinbase account anywhere in the Gulf or Egypt, assume your email or phone number could be in a phishing list, and only trust messages you can verify inside the official Coinbase app or website.

What is Amplitude and why did it have Coinbase customer data?

Amplitude is a product analytics platform. Apps send it events such as screens viewed, buttons tapped and funnels completed, so product teams can see how people use the product. Many apps also attach user properties to those events, and if a team sends email addresses or phone numbers as properties, that personal data sits at the analytics vendor too. That is the design choice this incident puts under the spotlight.

How can my app avoid leaking customer data through analytics tools?

Send analytics vendors pseudonymous IDs instead of emails, phone numbers, names, national IDs or IBANs; mask text inputs in session replay; route events through a server-side proxy with a field allowlist; protect the vendor console with SSO and MFA and limit who can export; rotate project keys; set short retention; and sign a data processing agreement with a breach-notice deadline that lets you meet UAE, Saudi and Egyptian notification rules.

Related reading

Sources

Related reading

Related reading