Friday, 20 November 2026
NEXA NEWSHD
Science & Technology

TfL Data Breach Exposes Details of 265,000 Oyster Photocard Customers in Second Cyber Incident in Two Years

Transport for London has confirmed that the personal details of around 265,000 Oyster photocard customers may have been accessed in a cyber breach, in the second serious security incident to hit the capital’s transport authority in just over two years. The photocard website has been taken offline, the UK’s data protection regulator has been notified, and every affected customer is being told to change their password and security questions when the system returns.

According to TfL, the breach came to light on Monday 16 November 2026, when Oyster photocard customers began receiving emails asking them to create accounts they already had. The emails came from TfL’s own systems, the transport body confirmed, but were generated as a result of the compromise. TfL said it immediately took the photocard website down while the incident was investigated, and that it has since contained the breach and contacted those potentially affected.

“The protection of personal information is a priority for us, and I apologise to our customers affected by this incident,” Shashi Verma, TfL’s director of technology strategy and revenue, said in a statement reported by The Register. “We immediately took the TfL photocard website down while this was being investigated.”

The transport authority said its current assessment is that no passwords, bank or payment card details, or customer journey information were compromised, and that it believes the names and dates of birth of children holding Zip Oyster cards were unaffected. But the list of what was taken is still serious: according to the breach notifications TfL began sending to affected customers on Wednesday 18 November, and reported by the Press Association, the compromised data includes names and contact details — email addresses, telephone numbers and home addresses — along with dates of birth and security questions and answers.

TfL has found no evidence so far that the compromised data has been misused, according to BleepingComputer, and it has notified the Information Commissioner’s Office, the UK’s data protection regulator. The transport body has not disclosed how the attackers got into its systems, and the investigation is continuing. BleepingComputer reported that the estimate of around 265,000 affected customers is up from an earlier estimate of about 250,000, and that the figure may increase further as the investigation proceeds.

The existing photocards themselves still work. Passengers can continue to travel with them, and can top them up through ticket vending machines at London Underground and National Rail stations, according to the Press Association. What customers cannot do while the website is offline is apply for or renew a photocard online, or check their journey history — those tasks now have to go through TfL’s customer services team. TfL said it hopes to restore the affected website services as quickly as possible, but has given no date for their return.

How the breach was discovered

The first sign that something was wrong was not an alarm in a security operations centre. It was an inbox. On Monday 16 November, Oyster photocard customers who already held accounts began receiving emails asking them to create one. The messages were confusing enough on their own; what made them alarming was that they had plainly been sent through TfL’s own mail systems.

According to The Register, TfL confirmed that the emails were generated as a result of the compromise — in other words, the attackers had enough access to the photocard system to make it send messages in TfL’s name. Computer Weekly reported that Shashi Verma told the BBC the breach came to light when photocard users received the unexpected emails asking them to validate their accounts, prompting an internal investigation.

TfL’s response, once the problem was identified, was fast and blunt: the entire photocard website was taken offline the same day. “We immediately took the TfL photocard website down while this was being investigated,” Verma said, according to the Press Association. “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.”

That speed matters, and it is worth pausing on why. In a breach of this kind, the gap between discovery and containment is where the damage is done. Every hour a compromised system stays live is an hour in which more records can be pulled and more messages can be sent in the victim organisation’s name. TfL’s decision to take the whole photocard portal down — rather than patch around the edges while keeping it running — is the kind of trade-off that inconveniences hundreds of thousands of legitimate users but limits the blast radius. It is also, notably, the same trade-off TfL made in September 2024, when its previous cyberattack forced new photocard applications to be suspended for more than two months.

What TfL has not said is how the attackers got in. The Register reported that the transport operator “hasn’t disclosed how the perpetrators got into its systems”, and there is no indication yet whether the entry point was a technical vulnerability, a compromised credential, or something else entirely. That silence is normal at this stage of an investigation — organisations rarely publish attack vectors while they are still closing them — but it leaves the most important question about the incident unanswered for now.

What was taken — and what was not

The distinction between what the attackers took and what they did not take is the centre of this story, and TfL has been careful to draw it in detail. According to the notifications sent to affected customers, and reported by the Press Association and BleepingComputer, the data that may have been accessed includes full names, phone numbers, email addresses, home addresses, dates of birth, and security questions and answers.

One notification shared on Reddit, and quoted by BleepingComputer, lists exactly those fields. The Press Association quoted the email TfL sent to affected customers on Wednesday: “We identified some suspicious activity which affected our Oyster photocard website on 16 November 2026 and took action to limit access, including taking the photocard system offline. While we acted quickly to restrict this, this activity has unfortunately resulted in unauthorised access to the personal information contained in your web account. We apologise for this.”

Against that, TfL’s current assessment — repeated in every outlet that has covered the story — is that passwords, bank and payment card details, and customer journey information were not compromised. It also believes, according to The Register, that the names and dates of birth of children with Zip Oyster cards were unaffected.

That last point needs care, because it sits next to a fact that looks contradictory at first glance. The accounts that may have been affected include holders of Zip Oyster cards — the cards issued to children as young as five — as well as students, apprentices, care leavers, veterans, and Londoners aged 60 and over, according to The Register. If children’s cards are in the affected set, how can children’s details be unaffected? The answer, as TfL presents it, is that the two statements describe different things: the accounts affected are the web accounts attached to photocards, and the personal details accessed are those of the account holders — in the case of a child’s Zip card, typically a parent or guardian — while the children’s own names and dates of birth are assessed as not having been compromised. It is a distinction worth stating precisely, because it is the difference between a breach that touched children directly and one that touched the adults who manage their travel.

Even with passwords untouched, the haul is far from harmless. A name, a home address, a date of birth and a phone number together form the skeleton of an identity, and security questions and answers are the part of the haul that security professionals worry about most. Those answers are the keys used to prove who you are when you have forgotten a password — and, as BleepingComputer noted, they may be used in account access restoration, so customers should remain vigilant for suspicious activity. Unlike a password, a security question cannot simply be reset with a new string of characters and forgotten; the answers are facts about a person’s life, and they tend to stay true for years.

Who is affected

Oyster photocards are personalised smartcards, carrying the holder’s photograph, that give eligible passengers free or discounted travel across London’s public transport network. According to the Press Association, the customer accounts that may have been affected cover Zip Oyster cards in all three age bands — 5 to 10, 11 to 15, and 16-plus — along with 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 is what makes the breach different from a run-of-the-mill corporate data leak. The affected population is not a random cross-section of commuters. It is, by design, made up of the people London’s transport system gives concessionary fares to: schoolchildren, students, young people leaving care, apprentices, military veterans, and older Londoners. These are groups that include some of the most vulnerable people in the city — children, and young adults who have recently left the care system — and they are also groups that may be less equipped to spot and respond to the phishing and fraud attempts that typically follow a breach of this kind.

The scale is large in absolute terms. Around 265,000 people is roughly the population of a mid-sized British city. It is also worth setting against the scale of the network itself: BleepingComputer reported that TfL recorded 3.53 billion passenger journeys in 2025-26, including 1.78 billion bus journeys and 1.20 billion Tube journeys. The photocard system is a small corner of that network by volume, but it is the corner that holds the most sensitive personal information, because a photocard application requires proof of identity, a photograph, and a home address.

TfL said it has contacted the customers who may be affected, and the Press Association reported that the notification emails went out on Wednesday 18 November, two days after the breach was discovered. The company has also notified the Information Commissioner’s Office, as it is required to do when personal data is put at risk. Computer Weekly reported that TfL told the BBC the data leak affected users of the photocard system and that it had taken the system offline to prevent further malicious access.

What customers should do now

Despite its assessment that no passwords were compromised, TfL says it will ask all photocard customers to change their passwords, along with their security questions and answers, once the portal is restored. That advice, reported by The Register, is worth following — and the reason for it is straightforward. If the attackers hold your security questions and answers, they hold the fallback route into your account. A password that was never taken is of limited comfort if the answers that let someone reset it are in the wrong hands.

The same logic applies beyond TfL. Anyone in the habit of recycling passwords across multiple websites is being advised to change them elsewhere too, according to The Register, and BleepingComputer recommended changing passwords on other services where the same information was used. Security questions deserve the same treatment: if the same questions and answers are used at other sites, they should be rotated to new questions and answers, BleepingComputer reported.

There is also a practical point about the emails themselves. Anyone who received the original message asking them to create an account should ignore it, BleepingComputer reported. And anyone who receives a message claiming to be from TfL about this breach should treat it with caution: breaches of this kind are routinely followed by phishing attempts that use the stolen details — a real name, a real address, a real card type — to make fraudulent messages look convincing. The safest route is to go to TfL’s own website or call its customer services team directly, rather than clicking links in an email.

For the immediate future, the practical impact is limited but real. Existing photocards still work at the barriers, and top-ups are available from ticket machines, according to the Press Association. But anyone who needs a new photocard, a renewal, or a check of their journey history will have to go through customer services while the website is down — and there is no word yet on when it will be back.

The second breach in just over two years

This is not the first time TfL has had to tell Londoners that their data is in someone else’s hands. In September 2024, a cyberattack on the transport authority forced it to suspend new photocard applications for more than two months and disrupted online services including Oyster refunds. The scale of that incident only became clear over time. In March 2025, TfL told The Register it had notified more than 7 million customers following the attack, after hackers accessed systems holding customers’ names, email addresses and home addresses. Around 5,000 customers were contacted as a priority because their bank account details may also have been compromised.

The BBC later revealed that the data of about 10 million people had been stolen in the 2024 attack, according to a BBC report carried by Europe Says. The two figures — more than 7 million customers notified, and about 10 million people’s data stolen — describe different things, and the gap between them is itself a reminder of how breach numbers evolve: the first figure is the count of people an organisation has formally warned, while the second is the count of records an attacker is believed to have taken. Both can be true at once, and neither is the final word.

The 2024 attack cost TfL £29 million in losses and recovery costs, according to BleepingComputer. Two teenagers were subsequently charged in connection with the attack, which authorities linked to the Scattered Spider cybercrime crew, according to The Register. The two hackers pleaded guilty in June 2026 and were sentenced to five years and six months in prison, BleepingComputer reported. The Information Commissioner’s Office looked into that incident but opted not to take enforcement action against TfL, having deemed its response proportionate, according to The Register.

There is nothing at present to suggest the two incidents are related, The Register reported. But the comparison is unavoidable, and it is uncomfortable. The 2024 attack was attributed to a named criminal crew and ended in prison sentences. The 2026 breach has no named attacker, no disclosed entry point, and no established motive beyond the data itself. And it has happened to the same system — the photocard website — that was taken down in the earlier incident. A transport authority that has already spent £29 million on one breach, and already had its response judged proportionate by the regulator, now has to explain how the same corner of its estate was compromised again.

That is the question that will dominate the weeks ahead, and it is one TfL cannot yet answer. The investigation is continuing, the entry point has not been disclosed, and the final count of affected customers may still rise. What can be said now is that the response, in its first days, followed the playbook the 2024 incident wrote: take the system down fast, notify the regulator, contact the people affected, and say plainly what was and was not taken. Whether that playbook is enough — or whether the same system being breached twice in two years points to a deeper problem — is a question for the investigation and, in time, for the regulator.

Analysis: Why It Matters

The email that gave the game away

There is something darkly instructive about the way this breach was discovered. The attackers did not trip a silent alarm; they made the system do something visible and wrong. Emails went out to people who already had accounts, asking them to create one, and the customers themselves reported it. TfL’s own mail system was, in effect, turned into the attackers’ loudspeaker — and it was the noise that gave them away.

That detail matters for two reasons. First, it suggests the compromise was not a quiet, surgical extraction of a database. Sending emails through a victim’s own systems is a noisy, conspicuous thing to do, and it is the kind of activity that usually means the attackers had broad access to the photocard platform rather than a single stolen file. Second, it is a reminder that the earliest warning of a breach often comes from the people affected, not from the security team. The customers who reported those strange emails did TfL a service, and the speed of the response — the site down the same day — owes something to them.

There is a wider lesson here for any organisation that holds personal data. The systems that send routine emails to customers are part of the attack surface, not an afterthought to it. An account-creation email is a small, forgettable thing — until it is sent by someone who should not be able to send it, at which point it becomes the first public evidence of a breach.

Security questions are the real prize

Read the list of what was taken, and one item stands out from the rest. Names, addresses, phone numbers and dates of birth are the standard currency of a data breach — damaging, but familiar, and to some extent replaceable. Security questions and answers are different. They are the fallback mechanism for the whole account, the thing you use when the password has failed, and they are built out of facts that do not change: a mother’s maiden name, a first school, a first pet.

That is why TfL’s advice — change your password and your security questions when the portal returns — is the most important sentence in this story, and why it deserves more attention than it will probably get. Most people treat security questions as a formality, set once and forgotten. This breach is a reminder that they are credentials in their own right, and that a stolen answer can be used to walk through the front door of an account whose password was never touched.

It is also why the advice to change reused passwords elsewhere matters. The data in this breach is the kind of data that feeds credential-stuffing and identity fraud for years, not weeks. A home address and a date of birth do not expire. The people affected by this breach should expect to be more careful, for longer, than the news cycle will be.

Children are in the affected set — and that changes the stakes

The photocard system exists to give free or discounted travel to children, students, care leavers, apprentices, veterans and older Londoners. That is a policy choice London should be proud of, and it is also what makes this breach harder to shrug off than a leak from a retailer or a streaming service. The affected population includes children as young as five, and young people who have recently left the care system — people whose data deserves the highest standard of protection, and who are least able to protect themselves when it is exposed.

TfL’s assessment that the names and dates of birth of children with Zip Oyster cards were not compromised is reassuring as far as it goes, and it should be reported plainly. But it is worth being precise about what it does and does not mean. It does not mean children were untouched by this breach: their cards are in the affected set, and the adults who manage their accounts — parents and guardians — had their details accessed. A breach that reaches a child’s travel account through their parent’s details is still a breach that touches a child, even if the child’s own name and date of birth were not in the haul.

That is the standard against which TfL’s handling of this incident will ultimately be judged. Regulators, parents and the public will not only ask whether passwords were safe. They will ask whether a system built for children was protected as if children depended on it — because they do.

A repeat offence, two years on

The hardest question for TfL is not about this breach. It is about the last one. In September 2024, the same photocard system was taken down by a cyberattack that cost £29 million, exposed the data of millions, and ended with two teenagers in prison. The Information Commissioner’s Office looked at TfL’s response and decided not to take enforcement action, deeming it proportionate. That was a judgement about how TfL handled the incident — not a guarantee that it would not happen again.

Two years later, it has happened again, to the same system, and the entry point is still undisclosed. That does not mean the two incidents are related — The Register reported that there is nothing at present to suggest they are — and it does not mean TfL failed to learn from 2024. But it does mean the organisation now has to answer a question that no amount of good incident response can deflect: what was done after 2024 to make the photocard platform harder to breach, and why was it not enough?

There are fair answers to that question, and there may be good ones. Security is not a state that is achieved once and kept; it is a contest, and the attackers get to choose the time and the place. A system can be substantially better protected than it was and still be breached. But the public case for that argument has to be made with evidence — with specifics about what changed, what was tested, and what the investigation finds — and TfL has not yet made it. Until it does, the comparison with 2024 will do most of the talking.

The number to watch is not 265,000

Headlines will rightly lead with the figure of around 265,000 affected customers. It is a large number, and it is the number TfL has put on the incident. But it is also a number with a history of moving. BleepingComputer reported that the estimate is already up from about 250,000, and that it may increase further as the investigation continues. The 2024 incident offers a cautionary parallel: the numbers disclosed in the first days of that breach were far smaller than the numbers that emerged months later, when the BBC reported that the data of about 10 million people had been stolen.

The figure that matters more, in the long run, is not how many accounts were touched. It is how many of those people are actually harmed — how many receive a phishing email that uses their real address and their real card type, how many have an account taken over through a stolen security answer, how many find their details for sale. TfL has said it has found no evidence of misuse so far, and that is genuinely good news. But “no evidence so far” is a statement about the present, not a prediction about the future, and the history of data breaches is a history of stolen data being used months or years after it was taken.

So the number to watch is not 265,000. It is the number that follows it: the count of affected customers who report fraud, the count of phishing campaigns that use this data, and the count that emerges when the investigation closes. Those are the numbers that will tell Londoners whether this breach was contained in time — or whether the real damage is still to come.

What to Watch Next

  1. The final count. TfL’s estimate of around 265,000 affected customers has already risen once, from about 250,000. Watch for the final figure when the investigation closes — and for whether it rises again.
  2. How the attackers got in. TfL has not disclosed the entry point. The investigation’s finding on this point will determine whether this was a technical failure, a human one, or something else entirely.
  3. When the photocard website returns. The site has been offline since 16 November, with no date given for its restoration. Its return — and the password and security-question reset that comes with it — will be the first practical test of the recovery.
  4. Whether the stolen data is used. TfL has found no evidence of misuse so far. Watch for reports of phishing emails, account takeovers or fraud linked to the stolen details in the coming weeks and months.
  5. The Information Commissioner’s Office. TfL has notified the regulator. The ICO took no enforcement action over the 2024 breach; whether it takes the same view of a second breach of the same system is an open question.
  6. What changed after 2024. Expect scrutiny of what TfL did to harden the photocard platform after the September 2024 attack — and whether those measures were tested, and by whom.
  7. Support for the youngest victims. Zip Oyster cards cover children from the age of five. Watch for what TfL and the regulator say specifically about protecting children whose accounts were in the affected set.

Sources

About the Author — Abdul Mannan

Leave a Reply

Your email address will not be published. Required fields are marked *