Trump Mobile
Three thousand six hundred people is a small breach, and a complete one.
What happened?
A breach at Trump Mobile exposed data on more than 3,600 people. Reporting attributes the incident to a hacking group and describes names, home addresses, emails, phone numbers and order information as the exposed fields.
The entry method and the dwell time have not been established in public reporting at the time of writing. By the standards of this series the number is small, which is the reason it is worth covering.
What data was actually inside?
Names, home addresses, email addresses, phone numbers and order information.
No payment data and no identity documents, but the set is otherwise complete: a real name tied to a verified home address, a working phone number and a record of what that person bought. For a mobile service the order record also establishes the device and the service tier.
Who gets hurt and how?
Customers of a small carrier, and the smallness cuts both ways. Three thousand six hundred people is a manageable notification list, which is good. It is also a list where membership itself is identifying.
In a breach of eight million, the fact that someone appears tells you almost nothing about them. In a breach of 3,600 customers of a politically branded service, appearing on the list is a disclosed affiliation. The dataset is small enough that the inference is specific.
What did they think they were doing right?
A small customer base means a small attack surface, and a new service has less accumulated legacy than an established carrier. Both are genuine advantages.
The assumption that does not hold is that a small dataset is a low-value target. Value scales with completeness and inference, not with row count, and a short list of identified individuals can be more useful to an attacker than millions of anonymous rows.
What did they not know about their own data?
Nothing about the inventory is established in public reporting, and the honest answer is that this one is too thin to assess.
What can be said is structural. Small operators rarely have a data map, because the organisation is small enough that everyone believes they already know what is held. That belief is usually accurate about the systems and inaccurate about the contents.
The 3,600 figure arrived quickly, which is the advantage of scale working in the victim's favour for once.
If your business runs on databases, you probably have similar records, customer data, credentials, financial information. Do you know what's actually in yours?
Not sure where to start? How to find sensitive data across your estate
What does attribution look like the morning after?
Reporting names a hacking group, but attribution has not been established in the sources cited here and no leak site listing is described.
A small, politically salient target attracts actors motivated by attention rather than profit, which usually means publication rather than quiet resale.
What would have changed the outcome?
Nothing exotic. The field list here is the minimum a carrier needs to deliver service, so the lesson is not about collecting less.
It is about recognising that a small customer list of identified individuals is a sensitive asset in its own right, and sizing the controls to the sensitivity of the records rather than to the size of the company holding them.
Gyazo found out the hard way.
Your team could spend the next 6 months rebuilding systems, notifying customers, and answering legal questions. Or you could spend 24 hours finding out what's actually at risk.
Want to understand the process first? Read our guide to sensitive data discovery .