Transport for London has confirmed the TfL Oyster photocard breach, which may have exposed the personal details of around 265,000 Oyster photocard customers. The people affected did nothing wrong. They applied for a travel card, created an online account, and trusted a public transport system with the details needed to prove who they are.
That trust is the real story here. A photocard is not a simple payment card. It links to a person, a photo, an address, and an entitlement to free or discounted travel. When someone compromises the account behind that card, the risk is identity theft, convincing phishing, and account recovery fraud that can follow a person for months.

What happened in the TfL Oyster photocard breach
TfL says it became aware of the incident on Monday 16 November 2026. Existing Oyster photocard customers began receiving emails asking them to create an account, even though they already had a photocard account. Those emails came from TfL own mail systems. The compromise generated those emails. That detail matters, because the messages were not ordinary spoofed emails sent from an outside address.
They came through a trusted channel, which makes them harder for a normal customer to question. TfL took the Oyster photocard website offline on the same day while it investigated. It later said it had contained the incident, and it had notified the Information Commissioner Office, known as the ICO. On Wednesday 18 November 2026, TfL sent a notification email to customers it believed were affected, and the public disclosure followed on 19 November 2026.

How many people are affected by the TfL Oyster photocard breach
TfL estimates that the TfL Oyster photocard breach may have compromised the account details of around 265,000 Oyster photocard customers. That figure is an estimate, not a final count. BleepingComputer reported that the estimate had risen from around 250,000, and that the investigation was not yet complete, so the figure may increase further.
Readers should treat the number with care. The phrase may have had their account details compromised means TfL believes unauthorised access reached those accounts. It does not mean TfL has proved that anyone copied, read, or used every one of those records. TfL has said that if a customer did not receive the email on 18 November 2026, the information currently available suggests the incident did not affect that customer. Customers should still check spam and junk folders, and watch for an update.
Who may be affected
Oyster photocards give eligible passengers free or discounted travel across London public transport. They are personalised smartcards, and they carry the holder photo. TfL listed the following account types as potentially affected: Zip Oyster cards for ages 5 to 10, 11 to 15, and 16 and over; the 18 plus Student Oyster card; the 18 to 25 Care Leaver Oyster photocard; the 60 plus London Oyster photocard; the Apprentice Oyster photocard; and the Veterans Oyster photocard.
That list includes children, students, apprentices, care leavers, older Londoners, and veterans. It includes people who rely on discounted travel to get to school, college, work, or medical appointments. The inclusion of Zip Oyster cards needs careful explanation. On its current assessment, TfL said the incident did not compromise the names and dates of birth of children with Zip Oyster cards. That does not mean no Zip account was in scope. Parents and guardians should read the TfL notice for their own account.
What data was exposed
According to the customer notification shared online and reported by several security publications, the incident may have exposed the following customer data for affected accounts.
- Full names.
- Phone numbers.
- Email addresses.
- Home addresses.
- Dates of birth.
- And security questions and answers.
That combination is serious. Security answers are a weak point, because many answers are facts that do not change and are often reused. Attackers can use a name and an email address alone for spam. An attacker can use a name, a home address, a phone number, a date of birth, and a security question answer together to build a convincing identity. An attacker can use those details to impersonate a customer, to answer account recovery questions on another service, or to craft a phishing message that looks personal and therefore trustworthy.
What TfL says was not compromised
On its current assessment, TfL says the incident did not compromise passwords, bank and payment card details, customer journey information, or the names and dates of birth of children with Zip Oyster cards. The incident also spared photographs and copies of supporting documents, according to the TfL notice reported by Help Net Security. The incident affected only the Oyster photocard website, and TfL said it did not reach any other TfL websites or services.
Those limits matter, and they should be stated clearly. With no password exposure, an attacker did not get a TfL password to reuse directly. Without bank or payment card exposure, this is not, on the current assessment, a direct financial theft from a card. And with no journey information exposure, an attacker did not get a record of where a person travelled. A breach can still be serious without a password or a bank detail, because identity data alone can support fraud.
What TfL said
Shashi Verma, TfL director of technology strategy and revenue, gave the main public statement for the incident. Verma said that on 16 November 2026, TfL became aware that Oyster photocard customers were receiving emails asking them to create an account when they already had a photocard account. He said TfL immediately took the TfL photocard website down while this was being investigated.
Verma added that while TfL acted swiftly, it now believed that around 265,000 photocard customers may have had their account details compromised as part of this incident. He said TfL had now contained the incident, and that its current assessment was that the incident had not compromised any passwords, bank or payment card details, customer journey information, or names and dates of birth of any children with a Zip Oyster card. He also said TfL was continuing to investigate, but had already contacted affected customers.
What TfL has done so far
On 16 November 2026, TfL took the photocard website offline in response to the TfL Oyster photocard breach. That is a blunt but effective step. It stops further unauthorised access through that website, and it stops customers from entering new details into a system that is under investigation. The cost is disruption. Customers cannot access their online photocard accounts, renew online, or check journey history online while the site is down.
According to TfL, it has contained the incident. Contained, in this context, means TfL believes it has stopped the unauthorised access from continuing. It does not mean the investigation is complete, the website is ready to return, or that anyone has recovered the exposed data. TfL has notified the ICO, which is the United Kingdom regulator for data protection. Existing Oyster photocards remain valid for travel, and customers can still top them up at ticket vending machines at London Underground and National Rail stations.

Why this is the second incident in two years
This is not the first major cyber incident to hit TfL in recent years. In September 2024, attackers broke into TfL back office systems, cutting staff off from internal tools and email and halting new Dial a Ride bookings. The attack disrupted customer services, including Oyster refunds, and it left a large number of internal systems affected.
Later reporting linked the 2024 attack to Scattered Spider, a group known for social engineering and help desk impersonation. Two men, Owen Flowers and Thalha Jubair, pleaded guilty in June 2026, and Woolwich Crown Court sentenced each of them on 16 July 2026 to five years and six months in prison for the intrusion. The attack cost TfL an estimated 29 million pounds in loss and recovery costs, according to reporting based on National Crime Agency figures. The November 2026 incident is different in scope, because it affected only the Oyster photocard website, and TfL current notice provides no evidence linking it to the 2024 attack or to Scattered Spider.
Why the email detail should worry every organisation
The most instructive part of this incident is not the number. It is the way the breach surfaced. Customers received emails from TfL own systems asking them to create accounts they already had. The compromise generated those emails.
For a security team, that is a warning about detection. An attacker who can trigger outbound mail from a trusted system can use that trusted channel to reach customers at scale, to test which accounts exist, or to create a cover for a wider access. For a customer, the lesson is harder. The usual advice is to trust a message only if it comes from the official sender. That advice fails when someone compromises the official sender system itself. In that situation, the customer needs a second check. Does the message make sense. Did I ask for this. If the answer is no, stop, do not click, and contact the organisation through a channel you already know.
What affected holders should do now
If you hold an Oyster photocard, start with the TfL email from 18 November 2026. Check your inbox, spam, and junk folders for a message from TfL about this incident. If you received it, follow the TfL guidance in that message and in the latest TfL update. If you did not receive it, the information currently available suggests the incident did not affect your information, but you should still stay alert for a later update, because the investigation is ongoing.
Do not click a link in an unexpected email about your photocard, even if it looks like it came from TfL. Go to the TfL website by typing the address yourself, or call TfL Customer Services on 0343 222 1234. When the photocard website returns, TfL will ask all photocard customers to change their password, security question, and answer. Do that promptly, and change the same question and answer anywhere else you reused it. If someone contacts you and claims to have your personal information, do not pay them, do not engage, and report the contact through Action Fraud.
What to watch next in the TfL Oyster photocard breach
Several facts about the TfL Oyster photocard breach remain unknown at the time of writing. TfL has not said how the attacker gained access to the photocard website. Nor has TfL said how long the unauthorised access lasted, or whether the attacker copied data in bulk or accessed accounts one by one. TfL has not said whether anyone has put the data up for sale or shared it online, only that it has found no evidence so far that anyone has misused the affected data.
TfL has not given a confirmed return date for the photocard website, and it has not said whether it will offer additional support to affected customers, such as identity monitoring. Those gaps are not a reason to assume the worst, but they are a reason to keep watching. Customers should look for a further TfL update that answers three questions. What was the root cause. What has been changed to prevent a repeat. And what should each affected group do next, in plain language.
Practical takeaway from the TfL Oyster photocard breach
A transport card should be a simple thing. You tap it, you travel, and you forget about it until you need to renew it. The TfL Oyster photocard breach shows how much personal data sits behind that simple tap, and how quickly that data can become a target.
For holders, the takeaway is practical and immediate. Check for the 18 November email. Do not click unexpected links. Use the official TfL phone number if you need help while the site is offline. Change your password, security question, and answer when the portal returns, and change the same question and answer anywhere else you reused it. Stay alert for phishing that uses your name, address, and date of birth to sound genuine.
