People search Transport for London data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Transport for London-linked incidents, with headline counts up to 10M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Transport for London breach history matters
Transport for London operates in Transportation (United Kingdom). Across indexed rows, recurring themes include third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2024 — Scattered Spider; ~10M contact records; subset (~5k) Oyster refund / banking fields
Cataloged incident. Between late August and early September 2024 TfL detected intrusion attributed in UK reporting to the financially motivated “Scattered Spider” cluster, with significant disruption to online services and public estimates of roughly £39m impact. Customer data exfiltration was characterized as a large contact database: BBC reporting (March 2026) described verification of a stolen file on the order of ten million people with names, email addresses, fixed and mobile phone numbers, and physical addresses; TfL publicly ca Exposed categories include Broadly: names, emails, phone numbers, postal addresses; heightened cohort: possible bank account number and sort code via Oyster refund records. BreachHistory cites approximately 10M+ affected records in this row. See the tfl-scattered-spider2024 and canonical BreachHistory entry.
2023 — ~13,000 Ulez / Congestion Charge records via supplier MOVEit (Clop)
Cataloged incident. In mid-June 2023 Transport for London stated a third-party supplier using Progress MOVEit Transfer was caught up in the global Clop ransomware zero-day campaign (CVE-2023-34362). UK press summarized impact to TfL as on the order of 13,000 people with data from Ultra Low Emission Zone (Ulez) and Congestion Charge–related processing; the incident was distinct from TfL’s later 2024 direct enterprise intrusion. Exposed categories include Driver / charge-account contact and scheme data as described in TfL supplier narratives and trade press (categories not fully uniform in first-wave reporting). BreachHistory cites approximately 13K+ affected records in this row. See the tfl-moveit2023 and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Transport for London catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the Transport for London company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/tfl · Latest: tfl-scattered-spider2024.
Sources: BreachHistory catalog (2 rows for Transport for London), company and regulator disclosures cited in individual breach records.