TfL Says Oyster Photocard Breach Exposed 265,000 Customers’ Data
Personal details of about 265,000 Oyster photocard holders were exposed in a Transport for London data breach detected on Monday, November 16 — four months after two hackers were jailed for a 2024 attack that cost TfL an estimated £29m.
The compromised data includes names, contact details, dates of birth and security questions and answers, according to TfL. The operator says passwords, bank or payment card details, journey history and customer photographs were not taken, and that no names or dates of birth of children holding Zip Oyster cards were compromised.
TfL first noticed something wrong when customers began receiving emails asking them to create accounts they already had. The emails came from TfL’s own systems, generated by the compromise itself.
“We investigated, found that there had been a breach and shut down the system immediately, limiting the impact on customers,” Shashi Verma, TfL’s director of technology strategy and revenue, told BBC News. “No data about any child has been compromised in this.”
The photocard website has been offline since TfL took it down during the investigation, with a maintenance notice on TfL’s site confirming the outage. Existing photocards still work at ticket barriers, and passengers can top up at machines in Underground and National Rail stations, but anyone needing to renew a card or check journey history must contact customer services.
What the hackers got, and didn’t
The affected accounts span the discount-travel scheme: Zip Oyster cards for children as young as five, 18+ Student cards, 18-25 Care Leaver photocards, 60+ London photocards, Apprentice photocards and Veterans’ photocards. The Telegraph, which first reported the scale of the leak, said that bank card details were not thought to have been taken.

TfL is urging all photocard customers to change their passwords and security questions as a precaution — and to change them on any other online service using the same information. That last point is where the exposure bites hardest.
“This matters because organizations share themes in their security questions; it’s why there’s an industry joke about ‘asking for your mother’s maiden name’.”
Nathan Davies-Webb made that point to ITPro, which reported that leaked security questions and answers could let attackers unlock accounts on other services or craft more convincing social engineering attacks. Phishing tends to follow breaches; Cybersecurity Insiders flagged the risk of targeted scams and impersonation, particularly for younger cardholders.
Two breaches, two very different numbers
The contrast with the last incident is stark. In August 2024, Thalha Jubair, then 20, and 18-year-old Owen Flowers hacked into TfL’s Oyster card system and accessed personal information of millions of users; all 27,000 TfL employees had to change their passwords. ITPro put the potential exposure in that September 2024 database breach at up to 10 million people. This time, TfL says swift containment cut the number to roughly 265,000.
Verma said TfL carried out “extensive work” after the 2024 breach. “We learnt a lot of lessons and we have put a lot more security in place,” he told BBC News.
He also defended TfL’s cyber-defences against the suggestion the system should have been hardened further. “The system that has been breached was tested quite thoroughly last year,” he said. “The reality of the modern world is the ways in which people are able to find weaknesses have increased.”

“We are in a different world of cyber-security, almost month by month,” Verma added. “New tools [for cyber-hacks] are becoming available all the time. This is a very difficult game to keep up with. But we know, like every other organisation does, that if you’re an attractive target, you have to be prepared that somebody will come after you, and find a weakness and get inside.”
Where the reports disagree
One detail is unsettled. Cybersecurity Insiders put the affected figure at “nearly 250,000” and dated the incident to October 2026; TfL’s own customer email, quoted by Yahoo News UK and The Mirror, says suspicious activity hit the photocard website on 16 November 2026, and TfL’s stated estimate is around 265,000.
The Register, The Telegraph and the London Evening Standard all align with TfL’s November date and the higher figure. Cybersecurity Insiders is the outlier on both counts, and TfL has not addressed the discrepancy.
How the attackers got in is also unknown. The Register reported that TfL has not disclosed the entry method, and nothing at present suggests a link to the 2024 attack, for which the operator’s response was reviewed by the Information Commissioner’s Office without enforcement action.
This breach has been reported to the ICO, according to TfL. The regulator’s handling of the 2024 incident — deemed proportionate, no penalty — sets the benchmark for what follows here, and the ICO has not said whether it will investigate this one.
Who pays for the cleanup
The operational cost is already visible: a closed website, suspended new photocard applications, and a customer services team absorbing renewals and journey-history queries by phone. The financial exposure sits elsewhere — in incident response, security remediation and regulatory risk. TfL’s experience shows why public-sector operators and large enterprises keep incident response and data-breach counsel on retainer: when 265,000 records leak, the immediate technical fix is the cheap part.

Organizations managing large consumer data sets typically respond with external forensic investigation, notification management and credit-monitoring support — services sold by specialist cybersecurity consultancies and privacy law firms. Whether TfL deploys all of that will depend on what its investigation finds.
Verma apologised in his statement: “The protection of personal information is a priority for us, and I apologise to our customers affected by this incident.”
Transport for London, the local government body behind the photocard system, was created in 2000 as part of the Greater London Authority, succeeding the London Passenger Transport Board established in 1933.
It runs the London Underground, Docklands Light Railway, buses, taxis and river services, and introduced the Oyster card and contactless payments in the 2000s. In 2003 it introduced the London congestion charge, at the time the largest such scheme ever undertaken by a capital city, and in 2016 launched the Night Tube.
The open question is entry. Until TfL says how attackers got inside a system it says was thoroughly tested only last year, customers cannot judge whether changing a password closes the door the intruders used. “We hope to restore the affected website services as quickly as possible,” Verma said.