Transport for London disclosed on 19 November 2026 that a data breach discovered on 16 November 2026 at its Oyster photocard service may have exposed email addresses and account details of around 265,000 customers. Customers first noticed the problem when account-creation emails arrived from TfL's own mail systems. TfL shut the photocard website, started sending breach notifications to affected customers, and reported the incident to the UK Information Commissioner's Office. TfL has found no evidence so far that the affected data has been misused. An Oyster photocard is a travel smartcard that carries the holder's photograph and entitles the holder to free or discounted travel in London.
This is the second major breach at TfL inside two years, after an attack in September 2024 that cost the organisation £29 million. The 2026 incident differs in the channel used: TfL's own mail systems sent the messages that first alerted customers. Security questions and answers were among the data that may have been exposed. Those answers work as account-recovery credentials, and people commonly reuse the same ones across services. TfL recorded 3.53 billion passenger journeys in 2025/26, and a photocard carries the holder's name, address, date of birth and photograph.
Discovery on 16 November#
On Monday 16 November 2026, existing Oyster photocard holders began receiving emails that asked them to create an account. The request made no sense to people who already held one. Customers reported the messages to TfL, and those reports prompted an internal investigation. TfL confirmed to The Register that the emails had come from its own systems, generated as a result of the compromise. Shashi Verma, TfL's director of technology strategy and revenue, said: "We immediately took the TfL photocard website down while this was being investigated."
The photocard portal is still offline. Its message explains that photocard customers received emails asking them to create an account they already held, and that the portal has been taken down temporarily while the investigation continues. TfL has given no date for its return.
TfL says the incident is contained. Shashi Verma, TfL's director of technology strategy and revenue, said:
"Due to the speed with which this incident was identified and addressed, we believe that the number of customers who could have been affected was significantly reduced."
The organisation has contacted affected customers and notified the Information Commissioner's Office, the UK data protection regulator. It has not said how the attackers got into its systems, and no actor has been named. Customer reports prompted the investigation. The first public account appeared three days later, on 19 November 2026.
Data that may have been exposed#
TfL's breach notification to affected customers lists six classes of data that may have been exposed. BleepingComputer reported the list from a copy of the notification shared on Reddit, and the same list appears in the notification text quoted in a rail forum thread. Both sources call it data that may have been exposed, not data confirmed taken from TfL's systems.
| Field | May have been exposed |
|---|---|
| Full name | Yes |
| Phone number | Yes |
| Email address | Yes |
| Home address | Yes |
| Date of birth | Yes |
| Security question and answer | Yes |
| Password | No |
| Bank or payment card details | No |
| Journey information | No |
| Names and dates of birth of children with Zip Oyster cards | No |
| Photocard photograph | No |
Together, the fields carry more weight than any one of them alone. A name, a home address, a date of birth and a phone number are enough, combined, to support impersonation by phone or post. Add an email address and the same impersonation gains a channel that arrives in the inbox, addressed by name. The security question and answer is the most consequential item on the list. Security answers act as account-recovery credentials, and people commonly reuse the same questions and answers across services, so an answer exposed at TfL can be tried wherever the same question is asked.
Passwords, bank and payment card details, journey information, and the names and dates of birth of children with Zip Oyster cards were not compromised, according to TfL's current assessment. Photocard photographs were also not compromised, Neowin reported. The assessment reflects the position now, not a final finding, and the investigation is not yet complete. TfL has not said whether the attackers still hold the data, and no source read for this article states otherwise.
Photocard holders affected#
The affected accounts span the full range of Oyster photocards. Infosecurity Magazine listed the account types from a statement shared by TfL: Zip Oyster cards for ages 5 to 10, 11 to 15 and 16 and over; the 18+ Student Oyster card; the 18-25 Care Leaver Oyster photocard; the 60+ London Oyster photocard; the Apprentice Oyster photocard; and the Veterans Oyster photocard.
Zip Oyster cards go to children as young as five. TfL says it does not believe the names or dates of birth of any children with a Zip Oyster card have been compromised. The affected group includes Zip Oyster card holders. No breakdown of the 265,000 figure by card type has been given, and no statement has been made about how many of the affected accounts belong to children.
The 265,000 figure estimates how many customers may have had account details exposed. BleepingComputer reported that the figure had risen from an earlier estimate of about 250,000. No source read for this article states where the earlier 250,000 figure came from, and the investigation is not yet complete, so the figure may increase further. TfL has given this as its own caution, not as a prediction.
Existing photocards stay valid for travel while the portal is offline. Customers who need to renew a card or check their journey history can contact TfL Customer Services, on 0343 222 1234 according to Computer Weekly.
Email addresses and account recovery#
The breach shows why an email address held by a service counts as a recovery credential as much as a contact detail. The Oyster photocard account is tied to the customer's email address, and the security question and answer stored on that account are the fallback when the password is forgotten. Both were in the data that may have been exposed. An attacker holding the email address and the security answer has the two items most account-recovery flows ask for.
AliasFleet provides one email alias per service, so the address handed to each service is unique to that service. A breach at one service then exposes only the alias used for that service, and the alias can be paused or deleted without changing the customer's real inbox address. What is an email alias explains how a unique address per service works. The service does not prevent a breach, and it does not protect data already held by the service, such as the name, home address and date of birth TfL holds. It limits what a leaked address can be used for afterwards, because the address points back to a single service and can be cut off from that service alone.
What Oyster photocard customers should do now#
Once the portal is restored, all photocard customers will be prompted to change their password, security question and answer. BleepingComputer and The Register both reported that customers should not wait for the portal to return before dealing with reuse elsewhere. If the same security questions, or the same password, were used on other services, those should be changed now, since the answers may have been exposed. How to tell if your email has been hacked covers the signs that an exposed address is being used.
Customers who received the account-creation email should ignore it. Any further message claiming to be from TfL and asking for account details, a password reset, or a payment should be treated with suspicion, since the data that may have been exposed could give an impersonator the customer's name, address, date of birth and email address to quote back. Customers who notice suspicious activity on their account should report it to TfL.
Your address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.
Investigation and the 2024 breach#
TfL has said the incident is contained and the investigation continues. The organisation has not disclosed the intrusion route, has not named an actor, and has not said whether the attackers still hold the data. The figure of around 265,000 may change as the investigation proceeds. No source read for this article mentions compensation, credit monitoring or a similar offer.
This is TfL's second major breach in two years. In September 2024, members of the Scattered Spider group breached TfL's network, stole customer data and disrupted online services, including Oyster refunds. The attack cost the agency £29 million in losses and recovery costs. Two of the hackers pleaded guilty in June 2026 and were sentenced to five years and six months. The Register reported that in March 2026 TfL said it had notified more than 7 million customers following that attack, with about 5,000 contacted as a priority because their bank account details may also have been compromised, and that the ICO looked into the incident and opted not to take enforcement action. Nothing in the sources read for this article suggests the two incidents are related.
The 2024 breach and the 2026 breach differ in the data involved. The 2024 attack reached names, email addresses and home addresses, and bank account details may also have been compromised for about 5,000 customers contacted as a priority. Security questions and answers were listed among the data that may have been exposed in 2026 and were not listed in reporting of the 2024 breach. According to TfL's current assessment, bank or payment card details were not compromised in the 2026 breach. Email addresses were among the data held by TfL in both incidents and, in the 2026 incident, among the data that may have been exposed.
