Research

TfL's Oyster Photocard Breach Exposed About 265,000 People's Security Questions and Answers. If You Reuse Those Answers Anywhere, Change Them There First

TfL's Oyster Photocard Breach Exposed About 265,000 People's Security Questions and Answers. If You Reuse Those Answers Anywhere, Change Them There First

What to do first. If you hold an Oyster photocard (Zip Oyster, 18+ Student, 60+, Apprentice, Care Leaver or Veterans), treat the security question and answer on your photocard account as public. If you used the same question and answer anywhere else, such as a bank, phone carrier, email provider or utility, change it there today. Those answers are what a caller uses to talk a help desk into resetting your account. Next, if your photocard password is used anywhere else, change it on those sites now. TfL says passwords were not taken, but reuse is the habit attackers count on. Then expect scams: calls, texts and emails that know your name, address and date of birth and talk about your Oyster account, a refund, a renewal or "verifying" your details. TfL already has your details. Do not hand them over to anyone who contacts you, and call TfL Customer Services on a number you look up yourself.

What TfL has said

We could not read TfL's own notice. tfl.gov.uk returned HTTP 403 to our fetches on November 19, 2026, including the photocard maintenance page that BleepingComputer links. Everything below is TfL's words as quoted by BleepingComputer, The Register, ITPro and Yahoo News UK (This is Local London). Those four outlets report the same TfL statements, so read them as one source, not four confirmations.

  • When: TfL says it "identified some suspicious activity which affected our Oyster photocard website on 16 November 2026" (a Monday). Shashi Verma, TfL's director of technology strategy and revenue, said TfL became aware "that Oyster photocard customers were receiving emails asking them to create an account". Those were customers who already had accounts. BleepingComputer and The Register report the emails were sent from TfL's own systems as a result of the compromise.
  • What happened: TfL told customers the activity "has unfortunately resulted in unauthorised access to the personal information contained in your web account." "We immediately took the TfL photocard website down while this was being investigated," Verma said.
  • Who: about 265,000 Oyster photocard customers, meaning people with a photocard web account. BleepingComputer reports TfL's earlier estimate was about 250,000 and that the figure may rise. The photocards cover children (Zip Oyster), students, apprentices, care leavers, veterans and Londoners aged 60 and over.
  • What was exposed: full names, email addresses, phone numbers, home addresses, dates of birth, and security questions and answers (BleepingComputer, Yahoo News UK; ITPro lists "security questions" without answers).
  • What was not, per TfL's current assessment: passwords, bank and payment card details, and journey information. TfL also says the names and dates of birth of children with Zip Oyster cards were not compromised. ITPro adds customer photographs to that list.
  • Status: TfL says it has contained the incident, contacted affected customers and notified the Information Commissioner's Office. It says it has no evidence so far that the data has been misused. Photocards still work at the barriers. For renewals and journey history, go through Customer Services while the website is down. No return date has been given. When the portal comes back, TfL will make every photocard customer change their password, security question and answer.

What is not known

  • How the attackers got in. None of the sources we read names a method, a product or a CVE. Nothing published says whether this was credential stuffing against customer accounts, a flaw in the photocard site or access to a back end. Treat any account of the method that goes beyond TfL's statements as speculation.
  • Who did it. No group has been named and no claim has been reported in the sources we read.
  • Whether it is connected to September 2024. The 2024 attack on TfL was linked to Scattered Spider. It exposed names, email and home addresses for a customer base TfL later said it had notified more than 7 million people about, plus bank details for about 5,000 Oyster refund customers. The Register says there is "currently nothing to suggest" the two incidents are related. We have not verified a connection in either direction and do not claim one.
  • Contactless and regular Oyster accounts. Every source describes the photocard website and photocard customers. None reports contactless or standard Oyster web accounts as affected. That is an absence in the reporting, not a statement from TfL that they are safe. The anti-phishing advice applies to them too, because scammers will not check which account you hold.
  • Indicators. None published in the sources we read, so we have added nothing to the feed.

Why the security answers matter more than the address

Your name, address and date of birth are already in many breaches. A security question and its answer is different. It is a credential that was designed to be reused, and most people give the same answer, such as a mother's maiden name, first school or first pet, to every service that asks. A caller who has your name, date of birth, address and that answer can pass many phone-based identity checks. That is the help-desk social-engineering playbook attributed to Scattered Spider. Nathan Davies-Webb of Acumen Cyber made the same point to ITPro: the questions could enable identity fraud and phone scams.

The emails telling customers to "create an account" are a lesson too. They came from TfL's real systems, so they would pass the usual checks: correct sender and real infrastructure. In this incident the sender was genuine and the request was not. That is the reason to treat every Oyster-themed message this month on its content, not its sender.

What to do

  • Change any reused security question and answer at every other service, starting with banks, mobile carriers and email. Where a service lets you, set an answer that is a random string kept in a password manager rather than a true fact.
  • Change any password you reused from the photocard account.
  • Ignore the "create an account" email from November 16. When the portal returns, reach it by typing tfl.gov.uk yourself, not through a link in an email.
  • Treat unexpected calls or messages about Oyster refunds, renewals, fines or "account verification" as scams until proven otherwise. Hang up and call TfL on a number you looked up yourself.
  • Ask your mobile carrier for a port-out or SIM-swap PIN. Your phone number and date of birth were in the data.
  • Report suspicious contact to TfL, and in the UK to Action Fraud. Forward scam texts to 7726.
  • Assume that for this population, name, date of birth, address and a common security answer prove nothing. A callback to the number on file, or an in-app approval, holds up. A known answer does not.

How we know

Every fact about the incident comes from TfL statements as quoted in the four outlets listed below, read on November 19, 2026. TfL's own pages returned HTTP 403 to us, and we found no ICO statement on this incident. There is no CVE, exploit path or indicator to check against our edge sensors, and this post makes no detection claim.

Sources

  • BleepingComputer, Bill Toulas: Transport for London breach exposes 265,000 Oyster card users' data (November 19, 2026), https://www.bleepingcomputer.com/news/security/transport-for-london-breach-exposes-265-000-oyster-card-users-data/
  • The Register: TfL takes Oyster photocard website offline after attackers compromise customer accounts (November 19, 2026), https://www.theregister.com/security/2026/11/19/tfl-takes-oyster-photocard-website-offline-after-attackers-compromise-customer-accounts/5310985
  • ITPro: Oyster photocard breach: TfL takes system offline after 260,000+ customers affected by attack, https://www.itpro.com/cyber-resilience/data-breaches/oyster-photocard-breach-tfl-takes-system-offline-after-260-000-customers-affected-by-attack
  • Yahoo News UK / This is Local London, Joseph Reaidi: Hackers access details of 265,000 Oyster card customers in TfL cyber breach (November 19, 2026), https://uk.news.yahoo.com/hackers-access-details-265-000-150750904.html
  • TfL photocard maintenance page (returned HTTP 403 to us), https://tfl.gov.uk/contact-us/we-re-doing-maintenance-on-our-photocard-website

Read next: Uber drivers' data in the Fireworks AI breach: the third downstream victim

Get the free feed: our threat intelligence feed is free to register and is built for defenders without a budget. Register for the free STIX feed.


Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.

Get your free key → analytics.dugganusa.com/stix/register