Transport for London (TfL) has confirmed that an attacker reached the personal details of about 265,000 Oyster photocard customers through its photocard website. The exposed data includes names, email and home addresses, phone numbers, dates of birth, and security questions and answers. TfL noticed the problem on Monday 16 November 2026, when customers who already had photocard accounts started receiving emails asking them to create one. It took the photocard system offline, reported the incident to the Information Commissioner's Office (ICO), and began emailing affected customers on Wednesday 18 November. The 265,000 figure is the same in every report. Some headlines round it to "more than 250,000" (the Daily Mail) or "more than 260,000" (The Standard and the Telegraph), but they all quote TfL's own estimate of "around 265,000". This is the second time in just over two years that a cyber incident has taken the photocard service offline.
What Happened
According to TfL's director of technology strategy and revenue, Shashi Verma, the first sign of trouble came on 16 November. Photocard customers "were receiving emails asking them to create an account, when they already have a photocard account". The Standard reports that these emails came from TfL's own system but were triggered by the compromise. The BBC reports that TfL detected "suspicious activity" on the photocard website that day.
TfL took the photocard website down straight away and says the incident is now contained. Its notification email to affected customers, quoted by The Independent and This is the Coast, says:
"We identified some suspicious activity which affected our Oyster photocard website on 16 November 2026 and took action to limit access, including taking the photocard system offline. While we acted quickly to restrict this, this activity has unfortunately resulted in unauthorised access to the personal information contained in your web account. We apologise for this."
Verma said TfL believes that because it found and dealt with the incident quickly, the number of customers who could have been affected "was significantly reduced". Metro reports that TfL has so far seen no evidence that the data has been misused. TfL has not said who was behind the incident, and no group has publicly claimed it.
The photocard website is still offline while the investigation continues. Customers cannot apply for or renew photocards online, and they cannot log in to their online photocard accounts. Existing photocards still work for travel and can be topped up at ticket machines in London Underground and National Rail stations. TfL has asked customers who need to renew a photocard or discuss their journey history to call customer services on 0343 222 1234.
What Was Taken
TfL's notification email says the following were exposed:
- Full names
- Email addresses
- Home addresses
- Phone numbers
- Dates of birth
- Security questions and answers
TfL's current assessment is that the following were not compromised: passwords, bank or payment card details, journey information, and the names and dates of birth of children who hold Zip Oyster cards.
According to TfL's notice, as reported by Metro, the Daily Mail and This is the Coast, the possibly affected account types are:
- Zip Oyster (5-10, 11-15, 16+)
- 18+ Student Oyster
- 18-25 Care Leaver Oyster photocard
- 60+ London Oyster photocard
- Apprentice Oyster photocard
- Veterans Oyster photocard
Zip accounts appear on the affected list, yet TfL says children's names and dates of birth were not exposed. That suggests the exposed data in those accounts belongs to the adult who manages the account, usually a parent or guardian. TfL has not explained this distinction directly.
Security questions and answers are the most sensitive part of this data. A password can be changed. The answer to "mother's maiden name" or "first school" usually can't, and people tend to reuse those answers across banks, utilities and other services.
Why It Matters
This keeps happening to the same system. In September 2024, a cyber attack on TfL forced it to suspend new photocard applications for more than two months. At the time, TfL said about 5,000 customers had been contacted because their bank details might have been accessed. The BBC later reported that the data of about 10 million people had been stolen. The Standard reports that all TfL staff (27,000 people, by its count) had to reset their passwords in person after that attack. The ICO later cleared TfL of wrongdoing over how it handled the 2024 breach. Two incidents hitting the same customer-facing service within roughly 26 months will draw attention to how that platform is built and maintained.
The people affected are easy targets for scams. Photocards go to children, students, apprentices, care leavers, veterans and Londoners over 60. Several of those groups are frequent targets of fraud. Anyone holding a list of real names, home addresses, dates of birth and phone numbers, linked to a trusted public body, can write very convincing phishing emails and texts, for example "your Oyster refund is waiting" or "verify your photocard to keep your discount".
Exposed security answers weaken account recovery elsewhere. Many organisations still use knowledge-based questions to verify callers and reset accounts. With this data in circulation, those checks offer less protection for the people affected.
The early numbers may change. In 2024, the first public estimate of the impact turned out to be far lower than the final one. The 265,000 figure and the list of what was not taken are both described by TfL as its "current assessment". Treat them as provisional until the investigation ends.
The Attack Technique
TfL has not said how the attacker got in. Neither its public notice nor Verma's statement explains how the account-creation emails were triggered or how the data was reached.
What is known:
- The compromise affected the Oyster photocard website and the personal data held in customers' web accounts.
- The first visible sign was legitimate TfL emails asking existing account holders to create an account. The Standard reports that these were generated as a result of the compromise.
- TfL says passwords were not compromised, which points to the attacker reaching profile data without obtaining the password store.
A wave of unexpected "create your account" emails to existing users is consistent with misuse of the registration, lookup or account-linking process. That could mean an attacker sending requests in bulk to a weakly protected interface, or flaws in how the site checked who was allowed to see which account's data. This is analysis based on the observed symptoms, not something TfL has confirmed. No malware, attacker infrastructure or threat group has been publicly linked to the incident.
What Organizations Should Do
-
Monitor transactional email for unusual volume. In this case, the attack first showed up as an unusual burst of system-generated emails. Alert on sudden spikes in registration, password-reset and verification emails, and treat such a spike as a possible security incident, not just a deliverability problem.
-
Protect account and registration interfaces from bulk misuse. Apply rate limits, bot detection and per-object authorisation checks to every endpoint that creates, looks up or links customer accounts. Check that a request for account data can only return data belonging to the authenticated user, especially on old public-sector portals that have grown over many years.
-
Stop using security questions. Stored question-and-answer pairs are a liability when breached and weak protection when they aren't. Move account recovery to email or SMS one-time codes, authenticator apps or passkeys. If you must keep security questions for now, store the answers hashed, the same way you store passwords.
-
Limit the personal data held behind customer web accounts. Consider whether a public-facing account portal needs full home addresses, dates of birth and recovery answers available all the time. Keep eligibility checks in a separate system the web front end can't query directly, and keep data in the web layer to a minimum.
-
Prepare for phishing that follows a breach. If your organisation serves the same groups (students, older people, veterans, care leavers), warn customers in advance that you will never ask for card details or security answers by email or text. Point them to Report Fraud, the UK national fraud reporting service, as TfL has done. Fraud and identity verification teams should treat callers who already know a TfL customer's date of birth and security answer with extra suspicion.
-
Wait for the investigation to finish before closing an incident. TfL's experience in 2024 shows that first scoping estimates can be far too low. Build further forensic review into your incident response plans, and be prepared to send another round of notifications if the scope grows.
Sources: Oyster photocard holders’ personal data accessed in TfL breach - BB... | TfL issues apology to Oyster card customers over data breach after... | More than 250,000 Oyster photocard users accounts ‘compromised’ by... | TfL website hackers steal customers’ names and dates of birth | TfL data breach may have exposed 265,000 Oyster photocards | TfL website 'hacked' affecting hundreds of thousands of Oyster phot... | Hundreds of thousands hit by TfL 'data hack': Oyster customers acco... | Oyster photocard customers' 'account details compromised' - This is...