Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    London Oyster Card Transit in Blue

    TfL Oyster photocard breach: data of 265,000 holders accessed

    Oyster photocard site breached, detected on a Monday

    Transport for London says personal data of about 265,000 Oyster photocard holders was accessed after a breach found on the photocard website. The site is offline, so customers cannot apply for or renew a photocard online until it returns.

    BBC reports that TfL spotted suspicious activity on the site on a Monday. The Telegraph reports that TfL learned of the hack that day, after customers received emails asking them to create an account they already had.

    Zip Oyster to Veterans photocard accounts may be affected

    The 265,000 figure is TfL's own estimate of customers whose account details may have been compromised, as BBC reports it. The Telegraph gives a slightly different number: more than 260,000 people.

    The accounts that may be affected belong to these photocard holders, per BBC:

    • Zip Oyster cards for ages 5-10, 11-15 and 16+.
    • 18+ Student Oyster and 18-25 Care Leaver photocards.
    • 60+ London, Apprentice and Veterans photocards.

    BBC reports that the data covers customers' names, birth dates, postal and email addresses, phone numbers, and their security questions along with the answers. TfL says passwords, bank and payment card details, and journey information were not compromised, nor were names or birth dates of children with Zip Oyster cards.

    Shashi Verma apologises and says TfL contained the breach

    Shashi Verma, TfL's technology director, apologised to affected customers and said TfL acted swiftly; BBC gives his title as director of technology strategy and revenue.

    TfL took the photocard system offline to limit access and told the Information Commissioner's Office. The website stays offline while the investigation continues.

    Change your photocard password; travel is unaffected

    Photocard holders can keep travelling. TfL asks every photocard customer to update their password and security questions as a precaution, the Telegraph reports. Anyone who needs to renew a photocard or talk about journey history can call TfL customer services on 0343 222 1234.

    TfL's 2024 attack and the jailed hackers

    In September 2024, a cyber attack forced TfL to pause new photocard applications for more than two months. TfL then put the number of customers it contacted about possible bank-detail access at roughly 5,000, but BBC later revealed that about 10 million people's data had been taken. BBC reports that the ICO found no wrongdoing by TfL in how it handled that breach.

    The Telegraph reports that two hackers, Thalha Jubair, 20, and Owen Flowers, 18, were jailed about four months before this incident for a four-day attack on TfL in 2024, which it estimates caused about £29m of damage. After that attack, all of TfL's 27,000 employees had to change their passwords, the Telegraph says.

    The cause, date and restoration time remain unstated

    The coverage does not state what caused the breach or how the attackers got in, and it names nobody as responsible. It gives no calendar date, only that the breach was detected on a Monday, and no date for the website's return. It does not break down affected customers by account type, say whether the ICO has opened an investigation, or say whether TfL will offer compensation or support.

    Sources

    Image: Photo by Sasun Bughdaryan on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion