Skip to main content

About 265,000 TfL Oyster Photocard Accounts May Have Been Compromised, and the Site Is Still Offline

TfL says attackers compromised Oyster photocard customer accounts after customers received sign-up emails for accounts they already held. What TfL says was and was not taken, what it has not explained, and what to check on your own logins.

KBY News Desk8 min read
Concrete modern platform with benches columns and advertisements lighted with bright white illumination

Transport for London has told customers that about 265,000 Oyster photocard accounts may have been compromised, and the photocard website has been offline since the transport operator noticed something wrong on Monday 16 November. TfL says it has contained the incident, has told the Information Commissioner’s Office (ICO), and has no evidence yet that the stolen data has been used. It has not said how the attackers got in or when the site will return. Existing photocards still work at the barriers.

#How TfL found out

The first sign was not an alert on a dashboard. According to TfL’s statement to The Register, customers who already had a photocard account started receiving emails asking them to create one. TfL told the outlet those emails came from its own systems and were generated as a result of the compromise. Shashi Verma, TfL’s director of technology strategy and revenue, gave the same account to ITPro and said the photocard website was taken down immediately while the incident was investigated.

We think that detail is the most useful thing in the whole story for anyone who runs a customer login. An email saying “create your account” sent to someone who already has one means something touched the registration or account-recovery path in a way the service did not expect. TfL has not described what happened, so what follows is our reading and not its finding: an automated flood of sign-up or recovery requests, whether to test which email addresses are registered or to take over accounts, would produce exactly that pattern of confusing messages. If it is right, the customers’ own inboxes spotted the problem before any monitoring did.

#Who is affected, and what TfL says was and was not taken

The Register reports that the people whose accounts may have been compromised include holders of Zip Oyster cards, which are issued to children as young as five, as well as students, apprentices, care leavers, veterans and Londoners aged 60 and over. That makes the affected group unusually vulnerable, a point Brian Higgins of Comparitech made to ITPro when he said the group covers some of the most vulnerable people.

TfL’s account of the data is careful and it is worth reading the two reports side by side, because they stress different things.

  • TfL told The Register that no passwords, bank or payment card details, or customer journey information were compromised.
  • ITPro reports that the data is believed to include names, home addresses, phone numbers, dates of birth, email addresses and security questions, and that no banking or payment-related information is thought to be involved. ITPro also says passwords and customer photographs remain secure.
  • TfL’s current assessment, quoted by ITPro, is that the names and dates of birth of children with Zip Oyster cards were not compromised.
  • The Register observes that TfL is more forthcoming about what the attackers did not get than about what they did, and we think that is a fair description of how the statements read. A full list of fields is not given in TfL’s own words in either report, so treat the ITPro list as its reporting and not as a TfL inventory.

The security questions deserve attention. TfL says it will ask every photocard customer to change their password anyway, along with their security questions and answers, and to change passwords they reuse on other websites. Asking for new security answers is a strong hint that the old ones were in the data, even though TfL’s statement to The Register does not say so in terms.

#What TfL has not said

This is a short list and it matters. TfL has not said how the attackers got in. It has not said when the site will come back. It has not said whether the 265,000 figure is customers whose data was actually taken or customers whose accounts could have been reached, though its wording is “may have”. Nor has it said whether the attackers are the same people as in an earlier incident. The Register notes that there is nothing at present to suggest the two incidents are related, and we agree with that caution: it would be wrong to guess.

What TfL has said about the aftermath is practical. Existing photocards will still let holders through the ticket barriers. Anyone who needs to renew a photocard or check their journey history has to contact customer services while the website is out of action.

#The second breach in just over two years

TfL’s earlier cyberattack was in September 2024. The Register says that in March the operator told it more than 7 million customers had been notified, that the attackers had reached systems holding names, email addresses and home addresses, and that about 5,000 customers were contacted as a priority because their bank account details might have been exposed. Two teenagers were later charged, and authorities linked the attack to the Scattered Spider crew. The ICO looked at that incident and chose not to take enforcement action, judging TfL’s response proportionate, according to the same report.

Two points follow from that history. First, the 2024 attack was a break-in to back-end systems. This one began, on the evidence TfL has given, with customer accounts and messages that looked wrong to customers. Those are different failures with different fixes, and treating them as one story about “TfL being hacked again” hides that. Second, a regulator that was satisfied last time will look at what changed since. We expect the ICO to ask what monitoring was added after 2024 and why a pattern of strange registration emails was caught by customers. That is our expectation, not anything the ICO has said.

#What this means for people who run services with logins

Most readers of this site do not run a transport operator, but nearly everyone runs something that sends “create your account” or “reset your password” emails. Four checks come out of this incident.

  1. Count the messages. Look at how many registration, verification and password-reset emails your systems sent in the last week, by hour. A spike, or a batch addressed to people who already have accounts, is the warning TfL got from its customers. Put an alert on the count, with a threshold set from your own normal.
  2. Make the response the same whether the address exists or not. A sign-up form that says “that address is already registered” tells an attacker which email addresses to target. The wording should not reveal it, and the email should be sent only to the address owner.
  3. Retire security questions. Answers such as a first school or a mother’s maiden name do not change and are shared across organisations, so a leak at one place weakens the others. Nathan Davies-Webb of Acumen Cyber made that point to ITPro, and we agree with it. Replace them with a second factor.
  4. Brief your help desk now. After a breach like this the realistic risk is a convincing phone call or email from someone who already knows a person’s date of birth, address and security answers. If staff or their families hold Oyster photocards, tell them what TfL has said and what a genuine TfL message will and will not ask for. We cover the wider problem in our piece on detecting AI-generated phishing at scale.

For individual photocard holders, TfL’s own advice is the one to follow: change the password and the security questions and answers when the site returns, and change any password that was reused elsewhere. We would add one thing of our own. Do not act on any email or text that arrives in the meantime asking you to log in to a TfL account. The site is down, so a message that sends you to it is not from TfL’s genuine process.

#The UK angle and where we think this goes

TfL says it notified the ICO, which is what a UK organisation should do when personal data is exposed, and it has contacted those potentially affected. Because the group includes children and young people, the cost of getting the notification wording right is high: a parent should be able to tell from the first line whether a child’s record is involved. TfL says its current assessment is that children’s names and dates of birth were not compromised, and we would expect it to keep saying so only for as long as the evidence supports it.

Our position is that this is a significant breach for the people in it and a modest one for the technology industry. The number is large, the data is the kind that fuels fraud for years, and the apology from a named director is the right tone. What would change our view is any sign that the site’s recovery or registration process was weak by design, or that passwords were affected after all. TfL has said they were not. If it later says otherwise, we will update this story.

Our earlier coverage of a different breach, in which a supplier’s systems were the weak point, is in the Uber driver data story. The lesson there and here is the same: the first people to know something is wrong are often the customers, so give them an easy way to tell you and read what they send.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01The Register, TfL takes Oyster photocard website offline after attackers compromise customer accountstheregister.com
  2. 02ITPro, Oyster photocard breach: TfL takes system offline after 260,000+ customers affected by attackitpro.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on About 265,000 TfL Oyster Photocard Accounts May Have Been Compromised, and the Site Is Still Offline. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.

TfL Oyster Photocard Breach: 265,000 Accounts, Site Offline