Nov 20, 2026 · 8 min read
TfL Oyster Photocard Breach Puts 265,000 Customers at Risk
Transport for London took its Oyster photocard website offline on 16 November 2026 after its own mail systems started sending account holders emails they never asked for. Emails, phone numbers, home addresses, birth dates and security answers may be in someone else's hands, and the next email that claims to come from TfL deserves a hard look.
On Monday 16 November, people who already had a TfL Oyster photocard account opened their inbox to find an email inviting them to create one. The message came from TfL itself, and that was the problem. TfL later told The Register that those emails were generated because of a compromise of the photocard website. Three days later, the transport authority said around 265,000 photocard holders may have had their details taken, a figure BleepingComputer notes was up from an earlier estimate of 250,000 and may still rise.
Key Takeaways
- TfL says around 265,000 Oyster photocard account holders may have had their email address, phone number, home address, date of birth and security question and answer compromised after suspicious activity on 16 November 2026.
- TfL's current assessment is that passwords, bank or payment card details, journey information, photographs, supporting documents and the names and birth dates of children with Zip Oyster cards were not compromised.
- TfL's own mail systems sent the first sign of the incident, a wave of unwanted account creation emails, so a message that genuinely comes from TfL is not proof that it is safe.
- TfL emailed affected customers on 18 November and says it will email everyone again when the photocard site returns, asking them to change their password, security question and answer.
- The 2024 Scattered Spider attack on TfL cost a reported £29 million, according to the National Crime Agency, although no source links it to this incident.
What Happened to the TfL Photocard Website?
Attackers got into the Oyster photocard website, the portal Londoners use to apply for and manage discounted travel cards, and TfL pulled it offline as soon as it saw the activity. TfL's notice to photocard account holders puts it plainly: "We identified some suspicious activity which affected our Oyster photocard website on 16 November 2026. We took action to limit access, including taking the photocard system offline."
TfL has not said how the attackers got in, and no group has claimed the attack. The notice says only the photocard website was affected, and that "No other TfL websites and services are affected." Shashi Verma, TfL's director of technology strategy and revenue, told The Register: "We immediately took the TfL photocard website down while this was being investigated."
The timeline so far, from TfL and the reporting:
- 16 November 2026: account holders receive unexpected account creation emails, TfL spots the suspicious activity and takes the site offline.
- 18 November 2026: TfL emails the photocard holders whose information it believes was compromised.
- 19 November 2026: TfL puts the number at around 265,000, up from roughly 250,000, according to BleepingComputer, and confirms it has told the Information Commissioner's Office.
What Data Did the TfL Breach Expose?
TfL lists five kinds of personal data that may have been compromised: email address, phone number, home address, date of birth, and security question and answer. Reporting by BleepingComputer also includes full names. TfL says it currently believes these were not compromised:
- Passwords
- Bank or payment card details
- Journey information
- Names and dates of birth of children with a Zip Oyster card
- Photographs and copies of supporting documents
The people on that list are not a random slice of London. The Register lists the groups that may be affected: Zip Oyster holders, students, apprentices, care leavers, veterans and Londoners aged 60 and over. Zip cards go to children as young as five, so the parents who manage those accounts are likely among the 265,000.
Why Are Leaked Security Answers Worse Than a Leaked Password?
Leaked security answers are worse because you can change a password in a minute, but the answers people pick, like a mother's maiden name or a first school, stay the same for life and get reused across banks, mobile carriers and email providers. TfL itself asks anyone who used the same security question and answer elsewhere to change them. The full set leaked here is the classic account recovery bundle: a name, a date of birth, a home address and the answer to a secret question.
You cannot rotate your birthday or move house to escape a leak. The only part you control is the secret answer, so treat the old one as public.
What This Means for Your Inbox
This breach announced itself through email. The account creation messages on 16 November were not spoofed. They came from TfL's systems, which means the usual sender checks were no help. Gmail's authentication checks confirm that a message was sent by a server the domain authorizes, and mail sent from TfL's own infrastructure would be expected to pass them. A verified sender tells you who sent it, not who was in control.
Two parts of TfL's own guidance add to the confusion. Its notice asks customers to check spam for the genuine 18 November email, teaching people to rescue "TfL" messages from the folder built to catch fakes. And it promises another email to everyone once the photocard site is back, asking for a new password and security answer. That future email is exactly the message a copycat would forge, because 265,000 people are now waiting for it. After the Free Mobile breach, attackers sent phishing emails that copied the real templates.
Notification by email also has a reach problem. After the 2024 attack, TfL told the BBC it had emailed 7,113,429 customers and that the emails had a 58% open rate. TfL did not say how it measured opens, but open rates are normally counted with an invisible tracking image that loads when the message is viewed. If the same rate held this time, a rough projection, about 111,000 of the 265,000 photocard holders would not register as opening the warning.
Is This Connected to the 2024 TfL Cyberattack?
No public evidence links the two incidents, and The Register reports that nothing suggests they are related. The 2024 attack, attributed to members of Scattered Spider, ran from 31 August to 3 September 2024, and the National Crime Agency calls it the UK's biggest ever cyber crime case. On 16 July 2026, Thalha Jubair, 20, and Owen Flowers, 18, were each sentenced to five years and six months for it, and the NCA puts the damage at a reported £29 million in loss and recovery costs.
TfL at first said only "some" customers were affected in 2024. In March 2026, the BBC saw a copy of the stolen database and estimated it held names, email addresses, phone numbers and home addresses for around 10 million people. Anyone who appears in both datasets now has contact details from 2024 plus a birth date and security answer from 2026 exposed, a better impersonation kit than either leak alone.
What Does UK GDPR Require From TfL?
UK GDPR requires TfL to report a breach like this to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it. That is Article 33, which adds that a late report must come with reasons for the delay. TfL has confirmed it notified the ICO, but no public source gives the exact date, so whether it met the 72 hour window cannot be checked from outside.
Article 34 covers the people affected: when a breach is likely to result in a high risk to their rights and freedoms, the controller must tell them without undue delay and in clear and plain language. TfL emailed affected customers two days after discovery, but as 2024 showed, an email notice only reaches people who open it. The ICO decided in February 2025 that formal action over the 2024 breach was not proportionate. For a recent UK public sector comparison, see the police supplier breaches the watchdog flagged in October.
What Should TfL Photocard Holders Do Now?
Start with TfL's own advice, then close the gaps elsewhere. The NCSC's data breach guidance for individuals covers the same ground in more depth.
- Check whether you were notified. TfL says that if you did not get its email on 18 November, your information appears not to have been affected. Search your inbox and spam folder, but judge any message by its content, not its sender.
- Never act on a link in a TfL email. When TfL emails to say the site is back, type the TfL address into your browser yourself or use the TfL app. Ignore any unexpected account creation email, as BleepingComputer reports TfL advised.
- Replace your security answers everywhere you reused them. Begin with the accounts that hold your money and your inbox. Where a site lets you, use a random answer stored in a password manager rather than a true fact.
- Change reused passwords. TfL believes passwords were not taken, but it still advises changing any password you shared with the photocard account.
- Turn on two step verification for your email. Your inbox is the reset point for everything else, so it deserves the strongest protection you have.
- Expect calls and letters, not just email. Phone numbers and home addresses are in the set. If someone contacts you claiming to have your data, TfL says to report it to Action Fraud on 0300 123 2040.
You can keep travelling in the meantime. TfL says photocards still work, and renewals or journey history queries go through its customer services line on 0343 222 1234.
Looking Ahead
TfL has not given a date for the photocard site's return, and the 265,000 figure may grow as the investigation continues, according to BleepingComputer. The open questions are how the attackers got in and whether the data surfaces on criminal forums, as the 2024 database did. Until then, treat every TfL email as a prompt to go to the TfL site yourself, not as something to click. The TfL notice is where official updates will appear.