Transport for London has warned that around 265,000 Oyster photocard customers may have had personal account information compromised after suspicious activity was identified on its photocard website. The authority said the activity was detected on November 16, after some customers received emails asking them to create accounts even though they already had photocard accounts. TfL took the website offline while it investigated. In an update reported by ITV News on November 19, the authority said its current assessment was that passwords, bank or payment-card details and customer journey information had not been compromised.
The information that may have been exposed includes names, contact details such as email addresses, phone numbers and home addresses, dates of birth, and security questions and answers. TfL said some affected customers received direct notification explaining that unauthorised access had occurred to personal information in their web accounts. The authority also said it had notified the UK Information Commissioner’s Office. The number of potentially affected accounts is an estimate, and the investigation may refine the scope as the organisation reviews the incident.
Photocard services were taken offline while the incident was contained
The affected accounts cover several categories of Oyster photocard, including Zip cards for children and young people, 18-plus student cards, care-leaver cards, 60-plus London Oyster photocards, apprentice cards and veterans’ photocards. These accounts are used to manage concessionary travel products and associated online services. TfL said customers could continue to travel using their photocards and top them up at ticket vending machines in London Underground and National Rail stations, but they could not access the affected online photocard accounts while the website remained unavailable.
The distinction between the photocard and the online account is important for customers. TfL said the physical travel product remained usable, while online account access was restricted during the response. That reduced the immediate impact on journeys but left customers unable to use some account-management functions. The authority said customers needing to renew a photocard or query journey history could contact its customer-service teams. It had not provided a full restoration timetable in the cited report.
The incident began with suspicious account activity that prompted TfL to take the website offline. The public information does not describe the technical entry point, whether attackers exploited a software vulnerability, obtained credentials through another service or used a different access method. Nor does it establish whether the exposed data was copied in bulk or accessed selectively. Those details matter for understanding the cause, but they were not available in the public account at the time of reporting.
The reported exposure of security questions and answers deserves particular attention because such information can be used in account-recovery processes. The risk depends on the questions asked, whether answers are stored in a recoverable form, whether the same answers are reused elsewhere and what additional checks protect an account reset. TfL’s statement that passwords and payment details were not affected is reassuring within the scope of its current assessment, but customers should not assume that exposed personal information has no future misuse potential.
Customers who receive a direct notification should follow TfL’s instructions and be alert to messages that use their photocard details to appear legitimate. Attackers sometimes use accurate personal information to make fraudulent emails, phone calls or text messages more convincing. A message that claims to help restore an Oyster account should be checked through TfL’s official website or customer-service channels rather than through links or telephone numbers contained in an unsolicited message.
The incident also shows the sensitivity of concessionary travel records, which can involve children, students, older passengers and people receiving specific travel entitlements. TfL said its current assessment did not indicate exposure of names and dates of birth for children with Zip Oyster cards. That statement should be preserved accurately: it does not mean no information about any child was exposed, but that the authority’s assessment did not identify those particular data fields as compromised for that group.
TfL said it had contained the incident and was continuing to investigate what happened. It apologised to affected customers and said it hoped to restore the online services as quickly as possible. The next material updates will be the final affected-account count, the technical cause, confirmation of what data was accessed and the restoration of the photocard website. Until then, the current account is that about 265,000 accounts may have been affected, some personal details may have been exposed, and travel using existing photocards can continue.