T-Mobile confirmed a cyberattack on August 16, 2021, and the number of people affected grew to 76.6 million, with names, birth dates, Social Security numbers and driver's license data exposed in many records. CEO Mike Sievert apologized on August 27. T-Mobile later agreed to a $350 million class settlement in 2022 and a $31.5 million FCC settlement in 2024.
Originally published August 2021. Updated November 2, 2026.
What happened in the T-Mobile 2021 data breach?
The T-Mobile 2021 data breach was an intrusion into T-Mobile's systems in August 2021 that exposed customer and applicant data on tens of millions of people. T-Mobile's first public count rose from about 40 million former and prospective customers, 7.8 million current postpaid customers and 850,000 prepaid customers to 76.6 million people by November 2021, according to Reuters.
| Date | Event | Source |
| August 16, 2021 | T-Mobile blog confirms a cybersecurity incident without yet saying personal data was stolen | MSSP Alert |
| August 17, 2021 | T-Mobile says data on just over 40 million credit applicants was exposed | Associated Press |
| August 20, 2021 | T-Mobile says another 5.3 million records were accessed | MSSP Alert, citing T-Mobile |
| August 26, 2021 | John Binns, a 21-year-old American living in Turkey, tells the Wall Street Journal he was responsible | Associated Press |
| August 27, 2021 | Sievert publishes an apology and announces partnerships with Mandiant and KPMG | Light Reading |
| November 2021 | T-Mobile raises the count of affected people to 76.6 million | Reuters |
| July 22, 2022 | Plaintiffs file a $350 million class settlement | Keller Rohrback |
| June 29, 2023 | The court grants final approval | Keller Rohrback |
| September 30, 2024 | T-Mobile agrees to a $31.5 million FCC settlement | The Register |
| May 2025 | Settlement payments begin | Keller Rohrback |
How did the attacker get in?
The attacker got in through an unprotected router, according to John Binns, who told the Wall Street Journal he found it in July 2021 and used it to reach servers in a T-Mobile data center near East Wenatchee, Washington, per the Associated Press.
T-Mobile called the attack highly sophisticated. Binns told the Journal he got in with ease, and called the company's security awful, according to Threatpost. Binns also told the Journal that generating noise was one goal, and did not say whether he sold any data, per Light Reading.
What did Mike Sievert's apology say?
Sievert's August 27, 2021 apology, which ran about 1,200 words, said T-Mobile was truly sorry and that it had not lived up to the expectations it has for itself to protect customers, according to the Associated Press. It announced long-term partnerships with Mandiant and KPMG, two years of McAfee ID Theft Protection for affected customers and the Scam Shield service.
Light Reading noted a contrast with 2015, when former CEO John Legere pointed to credit vendor Experian as the cause of a similar breach, while Sievert put the blame on T-Mobile itself.
What did the response get right, and what did it miss?
The response got four things right and missed two. EPR's assessment is based on the dated record above.
- It named the incident and accepted responsibility without hedging.
- It arrived 11 days after the confirmation, with a named CEO instead of an unsigned notice.
- It committed to outside expertise, with two named firms.
- It offered a concrete remedy, two years of identity protection.
It missed the pattern. Cyber Daily and other outlets counted the breach as the fifth T-Mobile hack in four years, and the statement treated August as one event instead of the latest in a series. It also described a highly sophisticated attack while the self-identified attacker told the Wall Street Journal the entry was easy, which left readers choosing between two accounts.
How many times has T-Mobile been breached?
T-Mobile has been breached at least five times in four years by media counts through 2021, and the FCC counted three more incidents from 2021 to 2023. The Register counted at least seven breaches over five years.
| Year | Incident | Scale | Source |
| 2018 | Cyberattack on a database | 2.3 million of 77 million customers | BankInfoSecurity |
| 2021 | The August breach covered here | 76.6 million people | FCC, via Reuters |
| 2022 | SIM-swapping and phishing used to reach an internal reseller platform | Not stated in sources reviewed | FCC summary |
| January 2023 | Misconfigured API exposed customer account data | About 37 million accounts | FCC, via The Register |
What did the 2021 breach cost T-Mobile?
The 2021 breach cost T-Mobile at least $350 million in class settlement funds, $150 million in security spending and a $31.5 million FCC settlement. T-Mobile said it expected a pre-tax charge of about $400 million in the second quarter of 2022, according to an SEC filing quoted by Fierce Network.
| Item | Amount | Detail |
| Class settlement fund | $350 million | Covers about 76.6 million U.S. residents, with no admission of wrongdoing |
| Security investment | $150 million | Spending committed for 2022 and 2023 |
| Cash payments | $25, or $100 in California | Some class members could claim up to $25,000 for losses, per Reuters |
| FCC civil penalty | $15.75 million | Paid to the U.S. Treasury |
| FCC security spending | $15.75 million | Spent on cybersecurity over two years |
Judge Brian Wimes granted final approval on June 29, 2023, according to Keller Rohrback. Objectors appealed, and distribution of payments began in May 2025, nearly four years after the breach.
What should communications teams take from T-Mobile?
Communications teams should take five lessons from T-Mobile, each tied to a dated event.
| Lesson | Evidence | Action |
| A breach is a multi-year communications job | Payments began in May 2025 for an August 2021 breach | Plan updates for regulators, courts and customers across years, not weeks |
| Answer the pattern, not only the incident | Outlets counted the breach as the fifth in four years | State what changed since the last breach and what the company will report next |
| Give counts as ranges until they are final | The figure moved from about 48 million to 76.6 million | Say what is still being investigated and when the next update arrives |
| Check your story against the attacker's | T-Mobile said sophisticated while Binns said easy | Publish technical facts you can document, and avoid adjectives you cannot |
| Pair outside partners with named internal ownership | The apology announced Mandiant and KPMG partnerships, and the FCC's 2024 settlement still cited foundational security flaws | Announce who inside the company owns the fix and how progress will be reported |
For the first two days, see EPR's data breach response timeline, and for planning see how to build a crisis communications plan. Other cases are in the Data Breach Communications Archive, including Equifax, Change Healthcare and PayPal.