London's Transport Site Leaked 265,000 People's Security Answers. Would You Spot the Warning Sign on Yours?
The first warning was an email nobody had asked for. On 16 November 2026, Transport for London (TfL) says Oyster photocard customers started receiving messages from TfL's own system asking them to create an account they
The first warning was an email nobody had asked for. On 16 November 2026, Transport for London (TfL) says Oyster photocard customers started receiving messages from TfL's own system asking them to create an account they already had. TfL later said about 265,000 customers had personal details accessed, including the security questions and answers used to prove who they are. If you run a customer portal, that kind of unexpected system email is worth treating as an alarm, not as a glitch.
What happened
According to The Independent, TfL was alerted on Monday, 16 November, after cardholders reported those unexpected "create an account" emails. Shashi Verma, TfL's director of technology strategy and revenue, said: "On 16 November 2026, we became aware that Oyster photocard customers were receiving emails asking them to create an account, when they already have a photocard account. We immediately took the TfL photocard website down while this was being investigated."
In notices sent on Wednesday, 18 November, and in statements carried by the BBC, The Independent and The Telegraph, TfL said this activity led to unauthorised access to personal information in web accounts. The BBC reports that TfL puts the figure at about 265,000 Oyster photocard customers. Verma said TfL now believes "around 265,000 photocard customers may have had their account details compromised as part of this incident."
TfL has not said how the data was accessed, and it said it is still investigating. We are not going to guess at the method.
What was accessed, and what was not
TfL says the accessed details include names, email addresses, home addresses, phone numbers, dates of birth, and security questions and answers.
TfL also says its current assessment is that passwords, bank or payment card details, and journey history were not compromised. It added that the names and dates of birth of children with a Zip Oyster card were not affected.
The Telegraph reports that TfL has urged all photocard customers to change their passwords and security questions as a precaution, even though TfL says passwords were not compromised. The photocard website remains offline, so customers cannot apply for or renew a photocard online until it is restored. TfL says customers can still travel with their photocards, and The Independent reports they can still top up at ticket machines.
The Independent says TfL has officially reported the incident to the Information Commissioner's Office (ICO), the UK privacy regulator. Verma said TfL has "now contained the incident" and has already contacted affected customers.
The affected account types, according to TfL as reported by The Independent and The Telegraph, include Zip Oyster cards, 18+ Student, 18-25 Care Leaver, 60+ London, Apprentice and Veterans Oyster photocards.
This is not the first time this system has been taken down
The BBC says this is the second time in just over two years that the photocard system was taken down because of a cyber incident. In September 2024, a cyber attack forced TfL to suspend new photocard applications for more than two months. That was a separate incident. TfL has not said the two events are connected, and we are not treating them as the same attack.
Why this matters if you run a customer portal
Most small businesses will never run a city transport site. They do run login pages, account portals, and "create an account" or "reset your password" emails. The useful lesson is the warning sign TfL says it saw first: a burst of system emails that customers did not request.
Security questions and answers are a poor second lock once they leak. Unlike a password, a mother's maiden name or a first-school answer is often reused on other sites and cannot really be changed. If those answers are part of how customers log in or recover an account, a stronger method, such as a one-time code or an authenticator app, is the better choice.
Unexpected account-creation or password-reset emails can also be the first visible sign that someone is abusing a customer portal, even when the emails come from your own system. That is why volume matters: a sudden jump in messages nobody asked for is worth investigating the same day.
We have written before about how hard it is to tell which customer records were accessed after an incident, and about what can go wrong when a password-reset form is left weaker than the login page. The split between what your host handles and what you still need to check is the same here: the portal is your system, even if a vendor helps run it.
What to check on your own site
1. Watch the emails your own system sends
Ask your developer or email provider for a daily count of account-creation, "verify your email" and password-reset messages. If that number jumps and customers start reporting emails they did not request, treat it as an incident, not as a mail-server glitch.
2. Look at how customers recover a lost login
If your site still uses security questions, ask whether they can be replaced with a one-time code or an authenticator app. Once those answers leak, they are hard to take back.
3. Know what you would be able to say after a breach
If someone accessed customer records tomorrow, could you say which accounts were touched, and which fields? If the answer is no, that is a logging and access-control problem to fix before you need it.
4. See what strangers see
An investigation can close a hole in a portal. It does not tell you what else the site exposes. A free website security scanner can show what an outsider can see from the internet, without logging in.
FAQ
Were bank cards or travel history taken?
TfL says its current assessment is that passwords, bank or payment card details, and journey history were not compromised, and that children's names and dates of birth on Zip Oyster cards were not affected. It is still investigating.
How did this happen?
TfL has not said. The public reports describe unauthorised access after suspicious activity, not a method. We are not filling in that gap.
What if I am not in London and I do not have an Oyster card?
The useful part for a site owner is the warning sign and the leaked security answers. If your business sends account emails or stores security questions, the same checks apply.
The original version of this article is on the HackerMe Security blog.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.