On 26 June 2026 Trenitalia began emailing some of its customers about a security incident: unidentified external parties had gained unauthorised access to personal data linked to train tickets. The company said that login credentials and payment data were not involved. Months later, the incident is worth revisiting for a reason that outlasts the news cycle: when attackers hold your real journeys, dates and document details, the phishing that follows does not look like phishing. This article sets out what was confirmed, explains why leaked context is so effective for social engineering, and turns the case into practical steps for employees and for the companies they work for. For the fundamentals of defending against phishing, start with our phishing protection guide.
Key Takeaways
- Trenitalia confirmed unauthorised access to ticket-related personal data and said credentials and payment data were not involved.
- The data categories it listed include identity, contact and journey details, and, where present, identity document details and loyalty codes.
- Real context is what makes a lure convincing. A message that quotes your actual trip passes the "how would they know?" test.
- Your employees travel too. A breach in the news is the best moment to remind them how to verify and report.
- Prepare a template now, so the next time a big brand is breached you can warn staff within hours, not weeks.
What Is Confirmed
The facts below come from Trenitalia's communication as reported by Sky TG24 and LaPresse on 26 June 2026.
- What happened: unauthorised access by unidentified external parties to some personal data linked to travel tickets. The company said it stopped the anomaly, secured its systems and strengthened controls.
- Who was told: a subset of customers identified after internal checks, by email. No total number was published.
- Data that may be involved, "where present on our systems": identification data (name, surname, date and place of birth of the passenger, name of the purchaser), contact data (email, phone), travel data (route, date and time, ticket number), loyalty card codes, employer, type of offer, identity document details and data used to generate tickets.
- Data not involved, according to Trenitalia: account access data and credentials, and payment information such as card number, expiry date and security code.
- Authorities: Trenitalia notified the Italian data protection authority (Garante) and CSIRT Italia, and filed a complaint with the Rome public prosecutor. Sky TG24 reported that experts from ACN, the national cybersecurity agency, worked with Trenitalia's technicians after the attack, and that the Polizia Postale was investigating.
Some outlets carried claims that went further than the company's statement. We stick to what Trenitalia communicated.
Why Leaked Context Makes Phishing Believable
Most people have learned to distrust generic messages: "Dear customer, your account has been suspended". What they have not learned is to distrust a message that knows things only the real company should know. Travel data is a near-perfect raw material for that:
- It is specific. A route, a date, a departure time and a ticket number are details nobody would guess.
- It is timely. Trips have natural follow-ups (delays, refunds, changes, loyalty points), so a message about them never feels out of the blue.
- It carries urgency. Refund windows, fines and expiring points all come with deadlines.
- It links identity to behaviour. With a birth date and a document number, an attacker can impersonate a support agent who "verifies" you, turning the usual security check upside down.
Security professionals call this pretexting: building a believable scenario before asking for anything. We describe the technique in more detail in our article on social engineering attacks.
What the Lures Look Like
We will not reproduce real messages. These are the patterns to expect after any breach of travel data, and they work the same way for airlines, hotels and booking platforms:
| Pattern | What it says | What it wants |
|---|---|---|
| Refund or compensation | Your train on a given date was delayed; claim your refund here | Card details on a fake payment page |
| Document check | We need to re-verify the identity document linked to your ticket | A photo of the document, or a selfie with it |
| Loyalty points | Your points expire tonight; log in to convert them | Account credentials, then the saved card |
| Fine or irregularity (SMS) | An irregularity was found on your ticket; pay now to avoid a penalty | A small payment that hands over the card |
| Phone "support" (vishing) | The caller quotes your trip and birth date to prove they are genuine | A one-time code, a remote-access app or a bank transfer |
| Business travel (email) | An invoice or itinerary change for a colleague's trip | A payment to a new bank account, or a malicious attachment |
Advice for Employees and Customers
- Do not use links in messages about your trips. Open the official app or type the website address yourself, then check whether the refund, change or fine exists there.
- Treat knowledge as proof of nothing. A caller who knows your journey and birth date has not proved they work for the company. Hang up and call the official number.
- Never share one-time codes. No genuine support agent needs the code your bank or app just sent you.
- Change reused passwords. Trenitalia said credentials were not affected, but experts quoted after the incident recommended changing passwords as a precaution. If the same password protects other services, change it there too, and turn on two-factor authentication.
- Be careful with document photos. A request to send a picture of your identity card to "verify a ticket" is a red flag.
- Report, do not just delete. At work, use the report button or the address IT gave you. A report from the first person who receives a lure protects everyone after them.
For Companies: a Breach in the News Is a Training Moment
Your employees travel for work, book with personal and corporate accounts, and receive the same messages as everyone else, often on the phone they also use for company email. When a large consumer brand announces a breach, attention is high for a few days. That is the best moment to remind people what to do, and most companies miss it because they have nothing ready.
Prepare a template in advance
Write a short internal notice now, with blanks for the brand and the data involved: what happened (in one sentence, from the company's own statement), what attackers might send, what to do, and how to report. Agree who approves and sends it. When the next breach hits the news, you fill in the blanks and send it the same day.
Run a themed exercise, responsibly
A simulation built around the theme of the moment, such as a "travel refund" email, tests whether the reminder worked. Keep it fair: the goal is to build a reflex, not to catch people out, and a click should lead to a short lesson rather than a reprimand. Measure the report rate, not only the click rate: a team that reports quickly is a team that detects for you. Our article on awareness training ROI covers which metrics matter.
Check what is already exposed
Leaked personal data rarely travels alone. If company email addresses or passwords are circulating from this or other breaches, attackers will combine them. Monitoring leaked credentials linked to your domain closes part of that gap.
A Template You Can Adapt
This is the kind of notice that works: short, factual, and focused on what the reader should do. Replace the parts in brackets.
Subject: [Brand] data breach: expect convincing fake messages
[Brand] has told customers that some personal data, such as [data categories from the company's statement], was accessed without authorisation. If you use [Brand] for work or personal travel, you may receive emails, SMS or calls that quote your real bookings.
What to do: do not use links in these messages; check through the official app or website. Never share one-time codes. If a caller knows your details, hang up and call the official number. If you reused your [Brand] password anywhere, change it.
How to report: use the report button in your mail client or forward to [security address]. Reporting a message that turns out to be harmless is never a mistake.
Keep the tone calm. The goal is to make reporting the obvious next step, not to frighten people.
The Breached Company's Duties, Briefly
Two regimes apply to an incident like this one. Under the GDPR, the controller must notify the data protection authority within 72 hours of becoming aware of a personal data breach (Article 33) and must inform affected people without undue delay when the breach is likely to result in a high risk to them (Article 34). Rail transport is also one of the sectors of high criticality listed in Annex I of NIS2; in Italy, Legislative Decree 138/2024 requires entities in scope to send CSIRT Italia an early warning within 24 hours of a significant incident, a notification within 72 hours and a final report within one month. Trenitalia said it had notified both the Garante and CSIRT Italia. For the details of the NIS2 reporting chain, see our guide to NIS2 incident reporting.
Checklist
- Write a reusable internal notice for "a brand our staff use has been breached" and agree who sends it.
- Make reporting easy: one button or one address, and a quick thank-you when someone uses it.
- Remind staff that knowing personal details is not proof of identity, on email, SMS or phone.
- Require a call-back on a known number before any change to supplier or travel-agency bank details.
- Turn on two-factor authentication for corporate travel and expense accounts.
- Run short, role-based phishing simulations through the year, and track report rates.
- Monitor leaked credentials tied to your company domain.
The part of this you can practise is the reflex: pause, verify through the official channel, report. Orizon Aware builds it with phishing simulations targeted by role and department, micro-lessons right after a click on the exact signal that was missed, and metrics on who reports and who improves. If you also want to know when credentials tied to your domain appear in leaks, Darkfield monitors credential leaks and ransomware leak sites.