← Breach analysis by the Dual Vulnerabilities framework

T-Mobile Credit-Application Data Breach (Unattributed, 2021)

2021 · United States · J - Information and communication · Data theft via network intrusion

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Data theft via network intrusion

Dual vulnerability type

Strategy to Execution

Evidence coverage: 5/6 stages, weight 30/60

Decisive stage: egress (tie-break: pre-breach condition) · Alternative: Expertise to Execution

Why this classification

(1) As one of the largest holders of credit-application personal data in US wireless, T-Mobile's strategic expectation was doctrinal and explicit: privacy policy and carrier/state data-protection duties require that sensitive customer data (SSNs, ID numbers) be retained only as long as needed and protected as crown jewels. (2) In practice the company still held name, date of birth, SSN and driver's license records of just over 40 million former or prospective customers who had once applied for credit; in August 2021 a criminal actor entered through a lab environment reached by impersonating a legitimate equipment connection, guessed passwords, moved across environments into database backup files and exfiltrated the data, and the intrusion surfaced only through claims posted in the cybercrime underground, while customer notifications were allegedly generalized and contradictory about SSN exposure. (3) The classification rests on the egress / data-governance stage, a pre-breach structural condition: the retention and protection requirement existed at policy and regulatory level but was never implemented in the data estate, so the exfiltration reached tens of millions of people who no longer had any relationship with the company - a knowing-doing gap between stated obligations and operational data handling, not merely weak security. The entry, containment and detection execution gaps (password-spraying succeeded; lab environments unsegmented; discovery by outsiders) are real and give Expertise to Execution the largest share, but the documented pre-breach condition wins the tie-break. (4) RM16 (Strategy to Execution lens): retention, minimisation and privacy requirements were not implemented in systems and processes - the company kept bulk SSN and driver's license records of former and rejected credit applicants, so the exposure comprised more sensitive data than any current business need required (causal role: Amplifying). RM22 (Strategy to Execution lens): authentication and account-protection requirements did not become enforced controls - password guessing and password-spraying succeeded across servers and rate limiting was allegedly never enabled (causal role: Enabling). RM30 (Strategy to Execution lens): isolation requirements were not realised in architecture and configuration - movement from lab environments into environments holding database backup files made the blast radius equal the entire retained data estate (causal role: Amplifying). RM39 (Strategy to Execution lens): notification workflows were not operationalised as designed - individuals whose SSNs were leaked received generalized notices while unaffected ones received specific reassurance, and third-party monitoring services informed many customers before the company did (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

Row description matches the incident T-Mobile disclosed on 17 August 2021 (just over 40 million former/prospective credit-applicant records); the class settlement defined the impacted population as approximately 76.6 million US residents. The description's 500m settlement matches press reporting of the July 2022 class settlement ($350m fund plus at least $150m committed security spend, final court approval June 2023); a separate $31.5m FCC consent decree (September 2024) resolved the CPNI investigations - the FCC order states the Bureau and T-Mobile disagreed on whether T-Mobile's programme violated any then-applicable standard of care, so the order's factual account is used, not any adjudicated violation. Actor is unattributed: the FCC order describes a criminal third party; Ars Technica reports an individual who claimed involvement to the WSJ - an unverified attacker claim, not relied on. Search surfaced references to an SEC disclosure investigation of T-Mobile that could not be confirmed in any source opened during this task; it is therefore not cited. Related rows: the cases directory holds no row-840, 841, 909 or 1857 file and no results exist for those rows in the output directory; row-994 is a different T-Mobile incident (MD5 password description) - nothing about related rows is asserted here. The case file's source_url carried a stray trailing slash; the citation uses the clean URL. Link check: t-mobile.com blocks automated access (HTTP 403); the page was opened and read during research.