Transport for London says about 265,000 Oyster photocard customers may have had account details compromised. The exposed fields include security questions and answers, alongside names, contact details and dates of birth. Those answers can matter wherever another service uses them to recover an account.
TfL detected suspicious activity on November 16 and took the photocard website offline. Jess Warren’s BBC report was published November 18 and updated November 19. It includes direct statements from Shashi Verma, TfL’s director of technology strategy and revenue, and his account of the discovery on BBC Radio London.
Evidence status: organization-confirmed breach, reported through BBC interviews and customer notices reviewed by BleepingComputer. The published accounts do not identify the entry vulnerability or establish an attacker identity.
The exposed records and exclusions need separate attention
Bill Toulas’s November 19 report lists possible exposure of full names, email addresses, phone numbers, home addresses, dates of birth, and security questions and answers. The approximate 265,000 figure remains an investigation estimate.
TfL says passwords, photos, bank and payment card details, and journey information were excluded. Verma also told the BBC that no data about children had been compromised. The reports specifically exclude the names and birth dates of children with Zip Oyster cards.
Zip-related account holders are among the potentially affected customer groups. That should not be rewritten as confirmed theft of children’s details. Other listed groups include student, care-leaver, apprentice, veteran and 60+ photocard account holders.
The current incident is separate from TfL’s 2024 breach. Victim estimates, banking exposure and attacker attribution from that earlier event should stay attached to that event.
Unexpected messages helped reveal the intrusion
Verma says customers began receiving unexpected account-validation emails on November 16. BleepingComputer reports that the messages came through TfL’s own mail systems as a consequence of the compromise. A familiar sender therefore offered insufficient reassurance about those particular messages.
TfL says it contained the incident, contacted affected customers and notified the Information Commissioner’s Office, the UK data regulator. BleepingComputer reports no evidence of secondary misuse at the time of its coverage. That is a current investigation finding, not proof that the information cannot be abused later.
Replace reused recovery information and use established contact routes
For affected account holders:
- Ignore the unexpected invitation to create an account. Reach TfL through its established photocard service page, rather than following an unsolicited message’s instructions.
- Change reused security answers on other services now. Start with services where those answers can reset a password or unlock an account. Choose unique answers that cannot be reconstructed from biographical facts.
- Follow TfL’s reset instructions when the portal returns. The reports say photocard customers will need to replace their password, security question and answer. Replace reused passwords elsewhere too, despite TfL’s assessment that passwords were excluded here.
- Verify requests separately when they quote real personal details. Knowledge of a home address or birth date is weak proof that a caller represents TfL after this disclosure.
Existing Oyster photocards remain valid for travel, according to TfL. The online application and renewal service remains unavailable in the reviewed coverage; customers needing renewal or journey-history help can contact TfL customer services.
Caveat: TfL’s containment and exposure assessments remain subject to investigation; the reporting provides no technical basis for naming a specific exploit or attributing the breach to AI.