Skip to content
cisonews.net

Incident · 8-K Item 8.01

T-Mobile reports data for about 37 million accounts obtained through an API

Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.

T-Mobile US, Inc. disclosed in a Form 8-K filed under Item 8.01 on January 19, 2023 that a bad actor had been obtaining data without authorization through a single application programming interface. The preliminary estimate covers about 37 million current postpaid and prepaid customer accounts, and the data was limited account information such as name, billing address, email and date of birth.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at T-Mobile, and when?

The company says it identified the activity on January 5, 2023. It says it began an investigation with external cybersecurity experts. The filing states that the source was traced and the activity stopped within a day of discovery. T-Mobile believes the first retrieval through the API came on or around November 25, 2022.

What T-Mobile customer data was taken?

The company describes the interface as able to provide only a limited set of customer account data. It adds the account number and details such as the number of lines and plan features. The filing says payment card information, Social Security numbers or tax IDs, government ID numbers, and passwords or PINs were not exposed. The 37 million figure is described as preliminary, and the filing notes that many accounts did not include the full data set.

How did T-Mobile respond?

T-Mobile says it has notified certain federal agencies and is working with law enforcement. It has begun notifying customers whose information may have been obtained. On finances, the company warns of possible significant expenses. It does not presently expect a material effect on operations.

What did T-Mobile's later reports add?

T-Mobile's annual report for 2022, filed on February 14, 2023, dates the start of the activity. The bad actor first pulled data through the API on or around November 25, 2022, about six weeks before T-Mobile spotted it on January 5, 2023. The same report says outside cybersecurity experts helped T-Mobile find and close the unauthorized access. It notified current, former and prospective customers whose information was involved.

The quarterly report for the period to March 31, 2023 drops "to date" from the count. Its finding is that data was taken for approximately 37 million current postpaid and prepaid accounts, though many did not include the full set of fields. The fields the API could return were name, billing address, email, phone number, date of birth, T-Mobile account number, and details such as the number of lines and plan features. None of the later reports gives a cost figure for this incident on its own.

DateWhat T-Mobile reported
on or around November 25, 2022Bad actor first retrieves data through the API
January 5, 2023Activity identified
January 19, 20238-K under Item 8.01: about 37 million accounts, preliminary
February 14, 202310-K: access found and closed; customers notified
April 27, 202310-Q: about 37 million accounts, without "to date"

How many Washington residents were affected?

Washington's attorney general lists a report from T-Mobile USA on January 19, 2023, for a breach dated November 25, 2022, with 772,593 Washingtonians affected. The information it records as compromised is: name, full date of birth and other information. That count covers Washington residents only.

What is still unknown?

The investigation was still ongoing at filing, and the company says it found no evidence that its systems or network were breached. The filing does not say how the API was reached, who was responsible, or what the final number of accounts will be. It also warns that further facts could change its view of the scope.

How this disclosure's timing compares

T-Mobile US disclosed 14 days after the discovery date its filing gives. Across the 22 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 3 days.

The rule behind an Item 8.01 filing

Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other telecommunications incidents on cisonews.net

  • Ericsson Inc., Breach notice, first disclosed March 9, 2026
  • Wytec International, 8-K Item 1.05, first disclosed August 29, 2025
  • AT&T, 8-K Item 1.05, first disclosed July 12, 2024
  • Frontier Communications, 8-K Item 1.05, first disclosed April 18, 2024; 751,895 affected in total (Indiana Attorney General)
  • DISH Network, 8-K Item 8.01, first disclosed February 28, 2023; 296,832 affected in total (Indiana Attorney General)

All telecommunications incidents

Sources

  1. 2026-11-06 · AWashington State Office of the Attorney General, data breach notifications list, published November 6, 2026
  2. 2023-01-19 · AT-Mobile US, Inc., Form 8-K (SEC EDGAR), published January 19, 2023
  3. 2023-02-14 · AT-Mobile US, Form 10-K for the period ended 2022-12-31 (SEC EDGAR), published February 14, 2023
  4. 2023-04-27 · AT-Mobile US, Form 10-Q for the period ended 2023-03-31 (SEC EDGAR), published April 27, 2023
  5. 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.