---
title: "TfL pulls Oyster photocard site; 265,000 holders’ details may be compromised"
summary: "TfL’s notice and its director’s account, 16 to 19 November: which five personal details 265,000 photocard holders may have lost, what was not taken, and what to do now."
url: https://www.thetechbag.com/blog/tfl-oyster-photocard-265000-offline
format: Note
desk: "Security"
area: "Threats & vulnerabilities"
region: Global
published: 2026-11-19
facts_checked: 2026-11-19
author: TechBag (The TechBag Journal)
tags: ["TfL data breach","Oyster photocard breach","TfL cyber attack","TfL photocard website down","Transport for London","Oyster photocard","Zip Oyster photocard","60+ London Oyster photocard","Shashi Verma","ICO","security questions","password reuse","Action Fraud","UK data breach"]
cover: https://www.thetechbag.com/blog/covers/tfl-oyster-photocard-265000-offline.png
---

# TfL pulls Oyster photocard site; 265,000 holders’ details may be compromised

*TfL’s notice and its director’s account, 16 to 19 November: which five personal details 265,000 photocard holders may have lost, what was not taken, and what to do now.*

Note · Security · Threats & vulnerabilities · By TechBag · Published 2026-11-19 · Facts checked 2026-11-19 · Canonical: https://www.thetechbag.com/blog/tfl-oyster-photocard-265000-offline

Transport for London has taken its Oyster photocard website offline after attackers reached customer accounts. TfL believes around 265,000 photocard account holders may have had their email address, phone number, home address, date of birth and security question and answers compromised. It spotted the suspicious activity on 16 November and emailed the account holders concerned on 18 November.[1] TfL has not said how the attackers got in.[2]

~265,000

photocard account holders whose details may be compromised

TfL

5

kinds of personal detail exposed, from home address to security answers

TfL

16 Nov

suspicious activity found; the photocard site taken offline

TfL

18 Nov

TfL emails the holders it believes were affected

TfL

## How TfL found out, and what was taken

Oyster photocards carry London’s fare discounts: Zip cards in 5-10, 11-15 and 16+ versions for children and young people, and photocards for students, apprentices, veterans and Londoners aged 60 and over.[3] TfL told The Register it first knew something was wrong on 16 November, when photocard customers began receiving emails asking them to create accounts they already had. The emails came from TfL’s own systems but were generated as a result of the compromise. “We immediately took the TfL photocard website down while this was being investigated,” said Shashi Verma, TfL’s director of technology strategy and revenue. TfL has told the Information Commissioner’s Office and says it has found no evidence yet that the data has been used.[2]

TfL’s own notice sets the boundary. Its current assessment is that no passwords, bank or payment card details, journey information, photographs or copies of supporting documents were compromised, nor the names and dates of birth of any children with a Zip Oyster card. Only the photocard website is affected; no other TfL website or service is.[1] Existing photocards still work at the barriers.[1]

## The last time: September 2024

**Figure: TfL’s photocard incident comes 26 months after customer data was accessed in 2024**

*TfL’s two customer-data incidents and what followed, September 2024 to November 2026*

| Date | Event | Detail |
| --- | --- | --- |
| Sept 2024 | Suspicious activity found | 1 September 2024; names and contact details of some customers accessed |
| Feb 2025 | ICO takes no action | 13 February 2025; the regulator closes the matter |
| Jun 2026 | Two plead guilty | June 2026; both later sentenced to five years and six months |
| Nov 2026 | Photocard site offline | 16 November 2026; account-creation emails alert TfL |
| Nov 2026 | ~265,000 emailed | 18 November 2026; holders whose details TfL believes compromised |

Source: TfL, cyber incident page (reviewed 16 July 2026) and photocard notice; The Register for 19 November · as of 19 November 2026, 11:30pm IST

On 1 September 2024 TfL found suspicious activity in its systems; names and contact details of some customers were accessed. The ICO said on 13 February 2025 that it would take no regulatory action. In June 2026 two people charged over that incident pleaded guilty; both were sentenced to five years and six months.[4] TfL has not linked the two incidents.[2]

## What a photocard holder should do

TfL says there is no need to contact it now. Holders should check spam folders for its email of 18 November; anyone who did not receive one is, on current information, not affected. When the site returns, TfL will email affected customers and ask them to change their password and security question and answer; anyone who used the same password or security answer elsewhere should change those too. Renewals and journey-history queries go to 0343 222 1234. Anyone contacted by someone claiming to hold their data should report it to Action Fraud on 0300 123 2040.[1]

Our viewWhy the security answers matter most

A password can be changed in a minute; a date of birth and a home address cannot. Together with a security answer they are what many help desks ask for to prove identity, so a reused answer is the detail to change first. For how stolen sign-ins lead to wider breaches, see [our Analysis of where identity controls fail](https://www.thetechbag.com/blog/iam-where-indian-companies-get-it-wrong).

How we did this

Figures as of 19 November 2026, 11:30pm IST

The 265,000, the five exposed details, what was not compromised, the 16 and 18 November dates and the advice are from TfL’s notice, which is undated; “around 265,000” is TfL’s figure, and TfL gives no breakdown by card type. The 16 November emails, Shashi Verma’s words and the ICO notification are what TfL told The Register. The 2024 incident, the ICO decision and the guilty pleas are from TfL’s own incident page. “26 months” is our arithmetic, September 2024 to November 2026. TfL has not said how the attackers got in or who they are, and we name no one.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [Transport for London, Information for Oyster photocard account holders](https://tfl.gov.uk/contact-us/we-re-doing-maintenance-on-our-photocard-website) — undated notice; describes events of 16 and 18 November 2026
2. [The Register: TfL takes Oyster photocard website offline after attackers compromise customer accounts](https://www.theregister.com/security/2026/11/19/tfl-takes-oyster-photocard-website-offline-after-attackers-compromise-customer-accounts/5310985) — 19 November 2026, 11:01 UTC
3. [Transport for London, Free and discounted travel (photocards)](https://tfl.gov.uk/fares/free-and-discounted-travel) — undated page
4. [Transport for London, Cyber security incident in September 2024](https://tfl.gov.uk/fares/free-and-discounted-travel/cyber-security-incident) — last reviewed 16 July 2026

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

Go deeper on TechBag

- [IAM costs $3 to $17 a user a month. The breach still starts at the password](https://www.thetechbag.com/blog/iam-where-indian-companies-get-it-wrong) — why reused passwords and security answers are the weak point
- [Amadeus breach hit at least ten airlines through one booking system](https://www.thetechbag.com/blog/amadeus-breach-airlines-one-supplier) — another breach of travellers’ personal data
- [Identity & access guides](https://www.thetechbag.com/browse/identity-access) — sign-in, MFA and the controls behind account takeover
