TfL says 265,000 Oyster photocard accounts may be compromised; its list has no names, BleepingComputer's does
TfL's own page says around 265,000 Oyster photocard account holders may have had five items of data compromised, after suspicious activity on 16 November 2026. BleepingComputer's report adds full names, an earlier estimate and a regulator notice that TfL's page does not print.
By Parminder Kumar Sharma · LinkedIn · · 16 min read
Two days to the emails, three days to the report, five items on TfL's page and six on BleepingComputer's (derived counts)
Transport for London's page headed "Information for Oyster photocard account holders" says TfL identified suspicious activity affecting its Oyster photocard website on 16 November 2026 and, on 18 November 2026, emailed the account holders whose information it believes to be compromised. Counting calendar days, because the page prints no hour, that is 2 days from identification to the emails and 3 days from identification to BleepingComputer's report of 19 November 2026 (all derived: 18 minus 16 is 2, 19 minus 16 is 3).
The page lists five items it says may have been compromised: email address, phone number, home address, date of birth, and security question and answers. BleepingComputer's list, which it attributes to the notifications, has six: the same five and full names (derived: 6 minus 5 is 1). The saved TfL page does not list names among the compromised items. It uses the word only for children with a Zip Oyster card, whose names and dates of birth it says were not compromised. This site's reading is that the extra item matters, because a name is what makes a message addressed to a person look genuine.
What those counts do not establish is most of what a customer wants to know: how the attacker got in, whether data was copied out or only exposed, when access began and ended, and what the final count will be. TfL's own wording is "may have had" and "currently available", and the page ends by saying it is continuously monitoring for any further impact. TfL is the victim and the only primary source here, and its page is its own account written for customers, so it leans to reassurance. That is not a reason to doubt it, and it is a reason to read each sentence for what it commits to.
This brief reads one primary (TfL's page) and one secondary (BleepingComputer, 19 November 2026). This site did not read the notification emails, the Reddit post BleepingComputer mentions, any page of the Information Commissioner's Office, or other press reports. It names no author, reporter or private individual.
What TfL's page says, in the order it gives it
TfL's page has seven short parts. In its order:
What happened. TfL says it identified "some suspicious activity" affecting the Oyster photocard website on 16 November 2026, and took action to limit access, "including taking the photocard system offline". It then says that, "while we acted quickly to restrict this", it believes around 265,000 photocard account holders "may have had" the five items above compromised.
Our response. On 18 November 2026 TfL emailed the account holders whose information it believes to be compromised, and advises checking spam or junk folders. A person who did not get that email is told that "the information currently available suggests" their information has not been affected. TfL's "current assessment" is that passwords, bank or payment card details, customer journey information, names and dates of birth of any children with a Zip Oyster card, photographs and copies of any supporting documentation were not compromised: six items.
Who is affected. TfL says the incident affected only the Oyster photocard website and that no other TfL website or service is affected.
Using your Oyster photocard. Cards still work for travel. Renewals and journey history queries are handled by phone (the page prints a number and says charges may apply; this site reprints no number).
What to do next. TfL says there is no need to contact it at this stage. It will email all affected customers when the website is restored and ask them to change their password, security question and answer, and advises changing any of those reused on other online accounts.
60+ London Oyster photocard customers. Cards continue to work, and TfL will be in touch to complete the annual address check.
How to report an incident. Anyone contacted by someone claiming to have their data should contact Action Fraud, which the page calls the UK's national reporting centre for fraud and cybercrime. It also says the National Cyber Security Centre has further guidance for individuals and families on data breaches.
The diagram puts the dates on a scale. The two dashed day cells are the days TfL names without an hour.
Set against the breach headings this site uses (access window, discovery, containment, notification, publication, and what was counted), the page gives some of them and leaves others blank.
The record under the breach headings, from TfL's page and BleepingComputer's report, as saved on 19 November 2026
| Heading | Stated | Not stated |
|---|---|---|
| Access window | Nothing on either page. | When access began, when it ended, whether it was one session or several. |
| Discovery | TfL: identified suspicious activity on 16 November 2026. BleepingComputer: the same date, after customer reports of emails asking them to create an account. | How TfL itself identified it (the TfL page); the hour. |
| Containment | TfL: took action to limit access, including taking the photocard system offline. BleepingComputer: TfL says the incident is now contained. | When access was limited or the system went offline; whether the website is still offline when you read this. |
| Customer notification | TfL: emails on 18 November 2026 to those it believes compromised; no email means current information suggests no effect. | How many emails were sent; whether that number equals the 265,000; how a customer can check without an email. |
| Regulator notification | TfL's page does not mention the ICO. BleepingComputer says TfL notified the ICO. | The date; any ICO record. |
| Publication | TfL's page is undated in the saved text. BleepingComputer is stamped 19 November 2026. | When TfL's page first went up and when it was last changed. |
| Records | Nothing counted in records. | How many records or rows were exposed. |
| Accounts and people | TfL: around 265,000 photocard account holders may have had details compromised. BleepingComputer: up from an estimated 250,000. | The final count; how many are confirmed and how many only possible. |
Which data: five items on TfL's page, six on BleepingComputer's
The comparison that matters most to a reader is the list of data. TfL's page prints the compromised items in one bracket, in one sentence: email address, phone number, home address, date of birth, and security question and answers. Counted as printed, that is 5. If "security question and answers" is split into a question and an answer it is 6, so this brief counts it as one item on both sides to keep the comparison fair.
BleepingComputer says one notification, shared on Reddit, states that the following customer data may have been exposed, and lists full names, phone numbers, email addresses, home addresses, dates of birth, and security questions and answers: 6 bullets. The saved TfL page does not list full names. This site did not see the notification, so it cannot say whether TfL's email contains names, or whether BleepingComputer's list is the email's own wording. The two pages disagree and this site resolves nothing.
The second band of the diagram is the list of what TfL says was not compromised. TfL prints six items; BleepingComputer's report prints four of them and does not mention photographs or copies of supporting documentation (derived: 6 minus 4 is 2). A reader who relied on the secondary would not learn that TfL says photographs and supporting documents were not compromised.
The security question. TfL lists "security question and answers" as possibly compromised, and says it will ask customers to change their password, security question and answer when the site is restored. BleepingComputer adds its own reading, that the exposure is "particularly concerning" because such answers can be used to restore access to an account. That reading is the secondary's and is not on TfL's page. This site's reading, labelled as such: a password can be replaced with a new random string, but a security answer is often a fact about a person, such as a place or a name, and an answer that was exposed stays exposed for any other service that asks the same question. Neither page prints which questions the Oyster website used, so how much of this applies is not known.
Where the two pages differ
BleepingComputer's report was published on 19 November 2026 and attributes its details to TfL, to the notifications and to unnamed customers. The differences below are in what each page says. This site resolves none of them, and on every point where TfL's page is silent, the article says the page does not say it.
TfL's page and BleepingComputer's report side by side, both as saved on 19 November 2026
| Point | TfL's page | BleepingComputer |
|---|---|---|
| Full names | Not listed among the compromised items. | Listed, in the notifications it describes. |
| What was not compromised | Six items, including photographs and copies of supporting documentation. | Four of them; photographs and supporting documentation not mentioned. |
| The count over time | One figure: around 265,000. | Says 265,000, up from an estimated 250,000 earlier (derived: up 15,000, 6.0 percent). |
| Whether the count may rise | Says it is continuously monitoring for any further impact. No statement that the investigation is open or that the figure may change. | Says the investigation is not yet complete and the figure may increase further. |
| Misuse | Not stated. | Says TfL found no evidence so far that the data has been misused. |
| Cause and discovery | Says only "suspicious activity". | Says TfL found the incident after customer reports of emails asking them to create an account, which came from TfL's mail systems as a result of a compromise. |
| Containment | Limited access and took the photocard system offline. | Says TfL has now contained the incident. |
| The ICO | Not mentioned. | Says TfL has notified the ICO. No date. |
| People who got no email | Says current information suggests their information has not been affected. | Does not say. |
| What to do with an earlier email | Does not mention it. | Says people who received the earlier email urging them to create an account should ignore it. |
| Who to tell | No need to contact TfL at this stage; Action Fraud if someone claims to have your data. | Says to report suspicious activity to the organisation as soon as possible. |
| An earlier incident | Not mentioned. | Recalls a 2024 attack on TfL, which it attributes to a named group, as background. |
Four of these are worth a sentence each.
The cause. BleepingComputer says the first sign was customers reporting emails asking them to create an account and that the emails came "directly from TfL's mail systems as a result of a compromise". TfL's page says "suspicious activity" and nothing about email. Whether TfL's own mail systems sent those emails, or another party did, and how, is not established by either saved page. It is the secondary's statement and this site did not see the emails.
"No evidence of misuse." It is BleepingComputer's statement alone. It reports TfL as having found no evidence so far. TfL's page does not say it. "So far" matters: an absence of evidence after three days is a state of the inquiry, not a finding.
The earlier estimate. BleepingComputer says the estimate had been 250,000. The TfL page prints one figure, so a reader of the page alone cannot see that a number moved. The saved pages do not say when the earlier figure was given or by whom beyond TfL.
The earlier incident. BleepingComputer's closing paragraphs recall a 2024 attack on TfL by a group it names, which it says cost £29 million in losses and recovery costs. TfL's page does not mention it. Neither saved page says the two incidents are linked, and this brief draws no link.
Friendly wording doing the work of evidence
Three pieces of wording on the page can be read as stronger than they are. None is a mistake. Each is a place where a comforting phrase stands where a measurement would be.
Wording on TfL's page, what it can support, and what it does not establish (read on 19 November 2026)
| Wording | What it supports | What it does not establish |
|---|---|---|
| The page's address and breadcrumb read "maintenance" (the page heading is "Information for Oyster photocard account holders", and the strapline "Update on the Oyster photocard incident.") | That the page is TfL's own notice for photocard customers and the Oyster photocard website is where it applies. | That the event was routine maintenance. The body says "suspicious activity" and "incident", and the saved text gives no sign when the label changed. |
| "may have had their details ... compromised" | That TfL has a group of 265,000 account holders whose details it cannot rule out. | That each of the 265,000 had details copied out. The pages do not say whether data was copied or only exposed. |
| If you did not receive an email, "the information currently available suggests" you are not affected | That TfL's present assessment is that the recipients of its 18 November email are the affected group. | A guarantee. It is an assessment as of the page's date, written to be revised, and BleepingComputer says the figure may rise. |
What TfL states, and what neither page states
Questions a reader will ask against TfL's page and BleepingComputer's report, as saved on 19 November 2026
| Question | Stated | Not stated |
|---|---|---|
| How did the attacker get in? | Suspicious activity affecting the Oyster photocard website. BleepingComputer: a compromise of TfL's mail systems is behind the account creation emails. | The entry route, the method, any weakness, any account used. |
| Was data copied out or only exposed? | TfL says details "may have had" been compromised. | Whether anything left the network, and how much. |
| How long was the access? | Nothing. | Any start, end or duration. |
| How many people? | Around 265,000 photocard account holders. BleepingComputer: up from an estimated 250,000. | The final count; the number of emails actually sent; whether any person holds more than one account. |
| Whose children's data? | TfL says names and dates of birth of any children with a Zip Oyster card were not compromised. | Whether any other data about children was involved. |
| Who did it? | Nothing. | Any actor, motive, demand or claim of responsibility. |
| Is it contained? | TfL: access limited, system offline. BleepingComputer: contained. | A date or an independent check; when the site returns. |
| Has the ICO been told? | BleepingComputer says so. TfL's page does not mention the ICO. | The date, the reference, the ICO's own record. |
This site read no ICO or other regulator page for this brief, and TfL's saved page gives no sign of an ICO reference. The ICO row rests on the secondary alone.
What to do, in order
Items 1 to 6 are TfL's advice in this brief's words. Items 7 to 12 are this site's suggestions and say so.
Take this with you
TfL's advice first, then this site's suggestions
- TfL: you can still travel with your Oyster photocard. To renew or query journey history, phone TfL; the page prints the number and says charges may apply.
- TfL: there is no need to contact TfL at this stage.
- TfL: check your spam or junk folder for TfL's email of 18 November 2026. Without that email, TfL's current information suggests your information has not been affected.
- TfL: when the photocard website is restored, TfL will email affected customers and ask you to change your password, security question and answer.
- TfL: if you have used the same password or security question and answer on any other online accounts, change them.
- TfL: if someone contacts you claiming to have your data, contact Action Fraud, and see the NCSC guidance for individuals that the page points to. If you hold a 60+ London Oyster photocard, your card continues to work and TfL will be in touch to complete the address check.
- This site's suggestion: treat any message that asks you to create or verify an account as suspect, even if it seems to come from a TfL address. BleepingComputer reports that the earlier account creation emails came from TfL's own mail systems, and TfL's page does not mention them.
- This site's suggestion: for a message asking you to act, go to TfL's own website by typing its address, not through a link in the message.
- This site's suggestion: do not reuse security answers. Where a service lets you choose, use an unrelated phrase rather than a true fact about yourself, and keep it in a password manager.
- This site's suggestion: expect targeted phishing that uses the five items TfL lists, your email, phone number, home address and date of birth, because those are enough to make a message look personal. If BleepingComputer is right, your name is also in play.
- This site's suggestion: list the other accounts that use the same email address and the same security answers, and change them at the same time as TfL's.
- This site's suggestion: if you have a 60+ card, wait for TfL's own contact about the address check and do not give details to an unexpected caller or message that claims to be it.
The UK angle, and what the saved pages leave out of it
The UK angle is real: the party is a UK public authority and the people are its customers, with a UK national fraud reporting centre and the NCSC named on the page. TfL's page names Action Fraud as "the UK's national reporting centre for fraud and cybercrime" and points to NCSC guidance for individuals. It does not mention the ICO, a legal deadline, a claim route or any help with identity theft. BleepingComputer says TfL has notified the ICO.
This site read no ICO, NCSC or UK GDPR page for this brief, so it makes no statement about what the law requires of TfL or what a customer can claim. It only records what the two saved pages print.
The question the page leaves open
TfL's page tells 265,000 account holders that a security question and answers may be in someone else's hands and that it will ask them to change them when the website returns. A password is easy to replace. If the answer you gave is a true fact about you, and the same answer protects other accounts, what exactly do you change?
Key facts
Sources
- PrimaryInformation for Oyster photocard account holders (strapline: Update on the Oyster photocard incident): TfL's own notice, undated in its text. Read in full from a rendered copy saved 19 November 2026 at 21:11 UTCTransport for Londonaccessed 2026-11-19
- Reported byTransport for London breach exposes 265,000 Oyster card users' data, 19 November 2026: a report used for the differences from TfL's page only. Read in full from a copy saved 19 November 2026 at about 20:25 UTCBleepingComputeraccessed 2026-11-19


