Publication note: This teardown preserves the supplied research and its evidence labels. Historical and regulatory statements reflect that research cutoff, not a fresh verification at publication. Control mappings are illustrative, not findings of ISO/IEC 27001 nonconformity. Kit document names and reference codes in the source are illustrative labels and may differ from the current catalog; documentation alone is not evidence of an operating control.
Executive Summary
T-Mobile US, Inc. (NASDAQ: TMUS) disclosed two major cyberattacks in the relevant period: the August 2021 intrusion (a settlement class of approximately 76.6 million U.S. residents 1) and the January 2023 API exploitation (~37 million current accounts 2 3).
Attribution correction. T-Mobile identifies those two major events and only unspecified unrelated non-material interim incidents 4. Although the FCC decree covers investigations spanning 2021–2023 5, primary sources examined do not substantiate a distinct August 2022, ~37-million-record incident involving stolen vendor credentials. Nor do T-Mobile SEC filings or official communications substantiate a June 2024, Snowflake-environment theft of ~126 million people 6 7 8. Both claims are excluded—not disproved as possible third-party claims. The 2015 Experian incident is historical context only 9.
A. Incident Facts and Incident Timeline
Company profile: T-Mobile US, Inc. (NASDAQ: TMUS), US wireless telecommunications. T-Mobile publicly lists ISO/IEC 27001 certifications in its Trust Center 10; precise scope, version, and certifying body are NOT INDEPENDENTLY VERIFIABLE from the public sources examined here.
Incident 1 — August 2021 Cyberattack
| Field | Detail |
|---|---|
| Intrusion start | On or before July 19, 2021 11 |
| Public disclosure | August 16, 2021 — acknowledgment of investigation into claims of unauthorized access 12 |
| Company confirmation | August 17, 2021 — unauthorized access to customer data confirmed 13 |
| 8-K filing | August 18, 2021 (evidence supports alternate event window; see Section F) |
| Attack vector | Sophisticated cyberattack; specific initial-access vector NOT INDEPENDENTLY VERIFIABLE from public sources |
| Systems and data | SSNs, driver's license/ID information, names, dates of birth, addresses, phone numbers, IMEI/IMSI numbers, account PINs for active prepaid customers 13 |
| Affected populations | ~7.8M current postpaid accounts (SSNs/DL); ~5.3M additional postpaid (no SSNs); ~40M former/prospective customers (SSNs/DL); ~667K former customers (no SSNs); ~850K active prepaid (names/phone/PINs); plus files containing IMEI/IMSI only 13 |
| MDL settlement class | ~76.6 million U.S. residents (preliminary approval) 1 |
| Financial data compromised? | No — T-Mobile confirmed no payment card, credit card, or financial account information was compromised 13 11 |
Incident 2 — January 2023 API Breach
| Field | Detail |
|---|---|
| Unauthorized access began | Approximately November 25, 2022 2 |
| Discovery | January 5, 2023 2 |
| Public disclosure / 8-K | January 19, 2023 3 2 |
| Attack vector | Exploitation of a single API 3 2 |
| Systems and data | Names, billing addresses, emails, phone numbers, dates of birth, T-Mobile account numbers, number of lines on account, plan features 3 |
| Excluded from exposure | Passwords/PINs, payment card information, SSNs/tax IDs, government IDs, financial account information 3 2 |
| Affected accounts | ~37 million current postpaid and prepaid customer accounts 2 3 |
| Containment | Within 24 hours of discovery 3 2 |
| Network compromise? | No evidence of broader network or core systems compromise 3 |
Note on the 2022 Period
The FCC consent decree confirms investigations covered 2021, 2022, and 2023 14 5. T-Mobile's 2024 Annual Report identifies August 2021 and January 2023 as major events, noting "other unrelated non-material incidents" for the interim 4. The characterization of an August 2022 event affecting approximately 37 million accounts via stolen vendor credentials is NOT INDEPENDENTLY VERIFIABLE from these primary sources and is excluded.
B. Security Failures (Documented)
Every finding is tagged: CONFIRMED (primary sources state it), REPORTED (secondary sources only), or ANALYTICAL INFERENCE (logical deduction from disclosed facts).
| Failure | Status | Basis |
|---|---|---|
| Broad access and lateral movement risk across systems holding SSNs and IDs | ANALYTICAL INFERENCE | FCC required zero-trust architecture and segmentation as remediation 5; the decree does not prove the precise pre-breach architecture. |
| Phishing-resistant MFA coverage across networks and systems | ANALYTICAL INFERENCE | FCC required phishing-resistant MFA 5 15; public evidence does not establish where MFA was or was not deployed. |
| Data minimization and inventory practices | ANALYTICAL INFERENCE | FCC required formal inventory, disposal, and minimization 5, but does not publish the prior control design. |
| API access control / configuration weakness | CONFIRMED | A single API was exploited from about November 25, 2022 to January 5, 2023 2. Rate limiting and exact authentication design are not disclosed. |
| Monitoring weakness | ANALYTICAL INFERENCE | The duration before discovery supports an inference, not a finding, of insufficient alerting. |
| Unauthorized access to customer PI and CPNI | CONFIRMED | FCC investigated potential Communications Act/CPNI violations 5. |
| Vendor oversight weakness | ANALYTICAL INFERENCE | The decree’s third-party scope and a separate 2015 settlement’s vendor remedies 9 do not prove a causal vendor failure in these incidents. |
Disclosure limit: Mandiant/KPMG review details, root cause, threat-actor identity, and API provisioning details are not public 16.
C. Financial Impact and Status
Scope note: No incident-specific response cost or insurance recovery appears as a distinct line item in examined SEC filings 6 7 17; stock price movements excluded from financial totals (see Section F).
| Category | Amount | Currency | Source | Status |
|---|---|---|---|---|
| 2021 MDL class settlement fund | $350,000,000 | USD | MDL No. 3019, W.D. Mo., preliminary approval July 22, 2022 1 18 | REPORTED — preliminary approval granted; attorneys'-fee award reversed and remanded by Eighth Circuit July 29, 2024 18; final net disbursement NOT INDEPENDENTLY VERIFIABLE |
| FCC civil penalty (covers 2021–2023 investigations collectively; not apportionable per incident) | $15,750,000 | USD | FCC Consent Decree, September 30, 2024 14 5 | CONFIRMED |
| 2015 Experian breach multistate AG settlement (historical context only; separate from 2021–2023 series) | $2,430,000 | USD | Minnesota AG, November 2022 9 | CONFIRMED — separate incident |
Exclusions — not added to confirmed-loss subtotal:
- $150M security-investment commitment (2021 MDL settlement): forward-looking investment, not a breach-loss payment; excluded.
- $15.75M FCC cybersecurity investment commitment: mandated alongside the civil penalty 5; forward-looking investment, excluded.
- $80M FCC location-data fine (April 2024): out of scope — unauthorized sale of customer location data to aggregators, not the 2021–2023 breach series 19 20.
- 2024 multistate deceptive-advertising settlement: out of scope — advertising practices, not data breaches 21.
Combined disclosed settlement fund and civil penalty (not a confirmed cash-loss total): $365,750,000
Alternate subtotal (excluding non-apportionable FCC penalty): $350,000,000
Caution: MDL figure reflects preliminary approval; the Eighth Circuit reversed the $78.75M attorneys'-fee award and remanded July 29, 2024 18; final disbursement is not verified in the supplied source material.
D. Regulatory and Litigation
FCC Consent Decree — September 30, 2024
The FCC resolved 2021–2023 Enforcement Bureau investigations with a $15.75 million civil penalty and $15.75 million cybersecurity-investment commitment 14 5 15. It examined PI/CPNI protection under the Communications Act and requires Board-level CISO reporting, zero trust/segmentation, phishing-resistant MFA, data inventory/minimization/disposal, and independent assessment 5. The penalty is not apportioned by incident. A separate April 2024 $80 million location-data-sales fine is out of scope 19 20.
2021 MDL Class Action
Over 40 class action lawsuits were consolidated into MDL No. 3019, In re: T-Mobile Customer Data Security Breach Litigation, W.D. Mo., before Judge Brian C. Wimes 22 23. Preliminary approval was granted July 22, 2022, certifying approximately 76.6 million U.S. residents and a California Settlement Subclass, with Kroll Settlement Administration LLC as administrator 1. Two class members challenged the $78.75 million attorneys'-fee request as excessive 18; on July 29, 2024, the Eighth Circuit reversed the fee award and remanded 18. Final administration status is not verified in the supplied source material.
Attorney General Actions
- 2015 Experian breach — multistate, November 2022: 41 AGs settled with T-Mobile for $2.43 million — a separate incident 9; T-Mobile was required to implement a Vendor Risk Management Program, vendor contract inventory, and vendor data-security requirements 9.
- 2021 breach investigation: 48 AGs investigated the August 2021 breach, noting 670,505 affected Minnesota residents 24. Resolution status is NOT INDEPENDENTLY VERIFIABLE.
- 2024 advertising settlement: 50-state deceptive-advertising settlement — out of scope 21.
E. Operational Disruption
T-Mobile's official communications describe no customer-facing service or network interruption for either confirmed incident. Post-2021 response — engaging Mandiant and KPMG, closing the access point, resetting PINs for approximately 850,000 prepaid accounts, and arranging two years of McAfee identity protection — constitutes incident response operations, not service outages 13 16. For the January 2023 API incident, T-Mobile confirmed no broader network compromise and shut down malicious activity within 24 hours of discovery, stating no material operational effect was expected 3 2. The public record supports incident-response disruption only — a distinction material to business-continuity analysis.
F. Stock Price Context
Methodology: Daily close prices, split-adjusted, dividends excluded; S&P 500 price index benchmark; beta assumed 1.0; excess return = TMUS minus S&P. Source: Yahoo Finance, October 15, 2026; all event dates confirmed trading sessions.
2021 Breach — Primary Window (August 16, 2021 Public Disclosure)
| Window | TMUS Close | TMUS Return | S&P Return | Excess Return |
|---|---|---|---|---|
| T−1 (Aug 13) | $144.94 | — | — | — |
| T0 (Aug 16) | $140.73 | −2.90% | +0.26% | −3.17% |
| T+5 (Aug 23) | — | −1.66% | +0.26% | −1.91% |
| T+20 (Sep 14) | — | −11.05% | −0.56% | −10.49% |
| T+60 (Nov 9) | — | −17.30% | +4.86% | −22.17% |
2021 Breach — Sensitivity Window (August 18, 2021 8-K Filing Date)
| Window | TMUS Close | TMUS Return | S&P Return | Excess Return |
|---|---|---|---|---|
| T−1 (Aug 17) | $140.67 | — | — | — |
| T0 (Aug 18) | $139.83 | −0.60% | −1.07% | +0.48% |
| T+5 (Aug 25) | — | −0.58% | +1.08% | −1.66% |
| T+20 (Sep 16) | — | −8.36% | +0.58% | −8.94% |
| T+60 (Nov 11) | — | −15.78% | +4.52% | −20.30% |
2023 Breach — Primary Window (January 19, 2023 Disclosure/8-K)
| Window | TMUS / S&P Close | TMUS Return | S&P Return | Excess Return |
|---|---|---|---|---|
| T−1 (Jan 18) | $145.90 / 3,928.86 | — | — | — |
| T0 (Jan 19) | $145.14 | −0.52% | −0.76% | +0.24% |
| T+5 (Jan 26) | — | +1.91% | +3.35% | −1.44% |
| T+20 (Feb 16) | — | +0.57% | +4.11% | −3.54% |
| T+60 (Apr 17) | — | +3.15% | +5.66% | −2.52% |
Interpretive limitations: Negative excess returns at T+20 and T+60 following the 2021 disclosure cannot be causally attributed to the breach alone; competing factors include market volatility, Federal Reserve policy, sector headwinds, and earnings announcements. The 2023 disclosure produced negligible event-day excess return (+0.24%), consistent with narrower data exposure and T-Mobile's guidance that operations would not be materially affected 2. The August 18 sensitivity window shows a smaller event-day excess return (+0.48%), suggesting partial pricing on August 16. Stock price movements cannot be causally isolated to breach disclosures and must not be used as a standalone impact measure.
G. ISO/IEC 27001:2022 Mapping
T-Mobile publicly lists ISO/IEC 27001 certifications in its Trust Center 10. The mapping identifies controls most relevant to documented failures; "violated" language is deliberately avoided; each row explains what adequate implementation would have reduced. Every Limit cell identifies constraints on the mapping inference.
| Documented Failure | ISO/IEC 27001:2022 Control | Reasoning | Limit |
|---|---|---|---|
| Broad-scope 2021 exposure | A.5.9 Inventory of information and other associated assets; A.5.12 Classification of information | Inventory and classification support scope-bounding and tiered protection for SSNs/IDs. | Limit: Public disclosures do not establish the pre-breach design; this is ANALYTICAL INFERENCE. |
| Access and lateral-movement risk | A.5.15 Access control; A.8.3 Information access restriction | Least privilege reduces blast radius; FCC required zero trust post-breach 5. | Limit: The prior architecture is not public; the mapping is ANALYTICAL INFERENCE. |
| MFA coverage | A.5.16 Identity management; A.5.17 Authentication information; A.8.5 Secure authentication | FCC required phishing-resistant MFA 5 15. | Limit: A remediation requirement does not prove its prior deployment state. |
| Exploited API / ~41-day dwell | A.8.9 Configuration management; A.8.15 Logging; A.8.16 Monitoring activities | Secure configuration, logs, and alerting reduce exploitable exposure and time-to-detect. | Limit: Authentication, configuration, and log details are undisclosed; mapping is ANALYTICAL INFERENCE. |
| Customer PI/CPNI exposure | A.5.34 Privacy and protection of PII | CPNI obligations align with PII protection; FCC investigated potential violations 5. | Limit: Specific pre-breach PII controls are not public. |
| Third-party or cloud-service risk | A.5.23 Information security for use of cloud services (conditional) | Cloud/service governance addresses supplier-chain risk. | Limit: The relevant relationship is not publicly identified; illustrative only. |
| Incident containment | A.5.24 Information security incident management planning; A.5.25 Assessment and decision on information security events; A.5.26 Response to information security incidents; A.5.27 Learning from information security incidents | Structured preparation and response support faster containment; 2023 was contained within 24 hours 2. | Limit: 2021 incident-management maturity is not fully public. |
| Segmentation risk | A.8.20 Networks security; A.8.21 Security of network services; A.8.22 Segregation of networks | Segmentation limits blast radius; FCC required it 5. | Limit: The mapping does not establish the former network design. |
What Blueprint by Aegora's Free Kit Would Have Addressed
The Aegora GRC kit documents below map to documented and inferred control gaps, establishing governance frameworks and documented evidence trails; they do not guarantee breach prevention.
| Risk Theme to Assess (not a finding of proven absence) | Supplied Document Label | Supplied Reference Code |
|---|---|---|
| Absence of phishing-resistant MFA and least-privilege access controls | Access Control Policy; Access Control Procedure | AEG-POL-002; AEG-PRC-001 |
| No structured incident management framework; 41-day API dwell time | Incident Management Policy; Incident Response Plan; Incident Response Playbooks | AEG-POL-018; AEG-PRC-009; AEG-PRC-010 |
| Insufficient logging and anomaly detection for API and system traffic | Logging and Monitoring Policy; Logging and Monitoring Procedure | AEG-POL-021; AEG-PRC-013 |
| Inadequate network segmentation enabling lateral movement | Network Security Policy; Network Security Procedure | AEG-POL-023; AEG-PRC-015 |
| Exploitable API and system misconfigurations | Vulnerability Management Policy; Vulnerability Management Procedure | AEG-POL-035; AEG-PRC-022 |
| Absence of structured threat intelligence to identify novel attack vectors | Threat Intelligence Policy; Threat Intelligence Procedure | AEG-POL-034; AEG-PRC-021 |
| Cloud and API service security gaps | Cloud Security Policy | AEG-POL-009 |
| Missing data classification for SSNs, government IDs, and CPNI | Data Classification, Protection and Retention Policy | AEG-POL-012 |
| Inadequate data and system asset inventory | Asset Register | AEG-REG-001 |
| Vendor oversight gaps (Experian 2015; FCC third-party scope 2021–2023) | Supplier Relationship Policy; Supplier Relationship Procedure; Supplier Due Diligence Checklist | AEG-POL-031; AEG-PRC-020; AEG-TPL-009 |
| Privacy and CPNI protection obligations | Privacy Policy | AEG-POL-027 |
| Cryptographic protection of stored PII (SSNs, government IDs) | Cryptographic Policy | AEG-POL-011 |
| Risk tracking and control-gap documentation | Risk Register; Statement of Applicability | AEG-REG-016; AEG-REG-017 |
These documents create governance and audit evidence; implementation reduces risk but cannot guarantee prevention.
Key Takeaways
- Correct attribution first. Primary sources establish two major events: August 2021 and January 2023. The proposed August 2022/~37M and June 2024 Snowflake/~126M claims are not substantiated as T-Mobile incidents.
- Secure APIs as production systems. The January 2023 API exploitation ran from about November 25, 2022 until discovery on January 5, 2023 2; authentication, configuration, logging, and alerting merit the same discipline as network services.
- Separate obligations from loss. The FCC headline consists of a $15.75M penalty plus a $15.75M security commitment; the decree does not allocate the penalty by incident 5. A settlement class is a legal construct, not the technical affected-population count 1.
- Build evidence, not promises. MFA, segmentation, inventory, monitoring, tested response, and the Aegora documents cited above reduce risk and demonstrate governance; none alone guarantees prevention.
Methodology and Limitations
Sources: T-Mobile SEC filings/newsroom, FCC decree, federal and state court records, and Minnesota AG announcements. Stock data: Yahoo Finance, October 15, 2026 (split-adjusted close; dividends excluded; S&P 500; beta 1.0).
Limitations: Mandiant/KPMG findings and root-cause detail are not public 16. SEC filings do not isolate incident response costs or recoveries 6 7 17. The fee appeal leaves final MDL disbursement unverified 18. ISO mapping is constrained by absent architecture evidence; several mappings are ANALYTICAL INFERENCE. The 2022 and 2024 claims are excluded for lack of primary corroboration, not disproved as third-party claims.
Sources
Primary Sources
- T-Mobile Forms 8-K/10-K: January 2023 API event; 2021/2023 incident history; no disclosed 126M Snowflake event 4 25 6 7 8 2
- T-Mobile newsroom and Trust Center: 2021 and 2023 disclosures, response, ISO listing 16 3 10 13 11 12
- FCC Consent Decree (Sept. 2024): breach-series resolution and remediation 14 5 15; FCC location-data decision (Apr. 2024), excluded 19 20
- Federal courts/JPML: MDL No. 3019 preliminary approval, consolidation, fee appeal 1 18 22 23
- Minnesota AG: 2015 Experian settlement, 2021 investigation, and out-of-scope advertising settlement 9 24 21
Blueprint by Aegora GRC publishes forensic breach teardowns to support CISOs, compliance officers, and IT managers in building documented information security programs. This article is analytical and does not constitute legal advice.
References
- https://www.mow.uscourts.gov/sites/mow/files/mdl/21-MD-3019-162.pdf (published 2022-07-22)
- https://www.sec.gov/Archives/edgar/data/1283699/000119312523010949/d641142d8k.htm (published 2023-01-19)
- https://www.t-mobile.com/news/business/customer-information (published 2023-01-19)
- https://investor.t-mobile.com/static-files/6c8f67e6-5485-457f-b57e-cb100ce39e34 (published 2024-02-02)
- https://docs.fcc.gov/public/attachments/DA-24-860A1.pdf (published 2024-09-30)
- https://www.sec.gov/Archives/edgar/data/1283699/000128369925000012/tmus12312024ex321.htm
- https://www.sec.gov/Archives/edgar/data/1283699/000128369925000012/tmus-20241231.htm
- https://www.sec.gov/Archives/edgar/data/1283699/000128369925000012/tmus12312024ex322.htm
- https://www.ag.state.mn.us/Office/Communications/2022/11/07_Experian.asp (published 2022-11-07)
- https://security.t-mobile.com/ (published 2026-10-15)
- https://www.t-mobile.com/business/2021-data-breach-protection (published 2021-08-16)
- https://www.t-mobile.com/news/network/cybersecurity-incident-update-august-2021 (published 2021-08-16)
- https://www.t-mobile.com/news/network/additional-information-regarding-2021-cyberattack-investigation (published 2025-11-05)
- https://www.fcc.gov/document/t-mobile-required-change-business-practices-after-data-breaches-0 (published 2024-09-30)
- https://docs.fcc.gov/public/attachments/DOC-405937A1.pdf
- https://www.t-mobile.com/news/network/cyberattack-against-tmobile-and-our-customers
- https://www.sec.gov/Archives/edgar/data/1283699/000128369925000153/tmus09302025ex991.htm
- https://ecf.ca8.uscourts.gov/opndir/24/07/232744P.pdf (published 2024-07-29)
- https://docs.fcc.gov/public/attachments/DOC-402213A1.pdf
- https://docs.fcc.gov/sites/default/files/TMobile_April2024.pdf
- https://www.ag.state.mn.us/Office/Communications/2024/05/09_WirelessCarriers.asp (published 2024-05-09)
- https://jpml.uscourts.gov/sites/jpml/files/MDL-3019-Tag-Along-Transfer-1-22.pdf
- https://www.mow.uscourts.gov/mdl-cases/23-md-3073
- https://www.ag.state.mn.us/Office/Communications/2022/03/02_TMobileDataBreach.asp (published 2022-03-02)
- https://investor.t-mobile.com/static-files/74cdc2c6-7b75-4893-9bf4-b0d7bcdf2fa8 (published 2024-02-02)