Was your data in the Amtrak breach?
Check whether your email address was in it
Check my exposureFree. No password — we email you a six-digit code. This breach and every other one your address appears in.
Amtrak (amtrak.com) suffered a data breach in 2026 that exposed around 2,147,679 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In April 2026, the hacking group ShinyHunters claimed they had breached Amtrak. The group typically compromises organisations' Salesforce instances before demanding a ransom and later, if not paid, dumping the data publicly. They subsequently published the alleged data which contained over 2M unique email addresses along with names, physical addresses and customer support records.
Breach record from Have I Been Pwned, CC BY 4.0. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Amtrak breach exposed and what each item actually enables:
Also listed in this breach: Email addresses, Names, Physical addresses, Support tickets.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Home addresses
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. - Names and usernames
Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts. - Email addresses
Treat any message referencing this service with suspicion, and never act on links in unexpected emails. - Confirm you were actually in it
Run a free scan before you spend time on the steps above.
This breach put your details on data-broker sites
Because Amtrak exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This breach is recent, so the data is actively traded and the risk is at its highest right now.
Remember: a breach can’t be “un-leaked” — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can’t, and remove what has been republished.
Frequently asked questions
What data was exposed in the Amtrak breach?
The Amtrak breach exposed home addresses, names and usernames, email addresses. Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
How many people were affected by the Amtrak breach?
Around 2,147,679 accounts were exposed, making it a large breach.
What should I do if I had a Amtrak account?
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Amtrak breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.