T-Mobile security breach exposed customer names, addresses, and more

It's unclear when the breach took place.

What you need to know

• On November 22, T-Mobile reported a security "incident."
• Customers' names, addresses, phone numbers, and more were breached.
• T-Mobile has made the issue known to the authorities.

Friday is usually cause for celebration for the end of another work week, but this time around, it's been quite a day for security concerns. Right after OnePlus announced that it encountered a security breach, T-Mobile also announced something similar.

On its website, T-Mobile says:

Our Cybersecurity team discovered and shut down malicious, unauthorized access to some information related to your T-Mobile prepaid wireless account. We promptly reported this to the authorities. None of your financial data (including credit card information) or social security numbers was involved, and no passwords were compromised.

The data accessed was information associated with your prepaid service account, including name and billing address (if you provided one when you established your account), phone number, account number, rate plan and features, such as whether you added an international calling feature. Rate plan and features of your voice calling service are "customer proprietary network information" ("CPNI") under FCC rules, which require we provide you notice of this incident.

T-Mobile does not indicate how many people this affected, or when exactly the breach occurred. Anyone that was impacted should have been contacted by now, and if not, will be shortly.

As mentioned above, this news comes not too long after OnePlus announced a similar incident in which it had a security breach where customers' names, numbers, email, and shipped addresses were compromised.

There's no way of telling right now if/how the two are connected, but it does seem like more than a coincidence for the two announcements to go up around the same time - especially considering that T-Mobile sells the OnePlus 7T.

Should we learn more, we'll be sure to update this accordingly.