TfL takes Oyster photocard website offline after attackers compromise customer accounts
The capital's transport operator told The Register it first became aware something was amiss on November 16, when Oyster photocard customers started receiving emails asking them to create accounts they already had.
- Among those whose accounts may have been compromised are holders of Zip Oyster cards – issued to children as young as five – as well as students, apprentices, care leavers, veterans, and Londoners aged 60 and over.
- Existing photocards will still let holders through the ticket barriers, though anyone needing to renew one or check their journey history will have to contact TfL's customer services team while the website is out of action.
- Despite the assurances about passwords, TfL says it will ask all photocard customers to change theirs, along with their security questions and answers.
"We immediately took the TfL photocard website down while this was being investigated," said Shashi Verma, TfL's director of technology strategy and revenue.
Transport for London (TfL) has copped to another cybersecurity breach, this time involving the account details of around 265,000 Oyster photocard customers.
- "The protection of personal information is a priority for us, and I apologize to our customers affected by this incident." TfL reckons its speedy response spared a considerable number of customers from having their details compromised.
- TfL says no passwords, bank or payment card details, or customer journey information were compromised.
- TfL says it has yet to find any evidence that the compromised data has been used and has notified the Information Commissioner's Office (ICO).
- The ICO looked into that incident but opted not to take enforcement action against TfL, having deemed its response proportionate.
- The transport operator says it has since contained the incident and contacted those potentially affected, though it is rather more forthcoming about what the hackers didn't get their hands on than what they did.
How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →