[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1xowdj3gke3vz":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":14,"contentUpdatedAt":15,"source":16,"sourceUrl":17,"sourceUrls":18,"pwnCount":21,"affectedCount":21,"affectedCountStatus":22,"affectedCountLowerBound":13,"affectedCountUnit":23,"hasEnglishDescription":4,"contentLocale":24,"availableLocales":25,"translations":27,"severity":30,"dataClasses":31,"description":36,"seoTitle":37,"seoDescription":38,"logoUrl":39,"isVerified":4,"isSensitive":4,"isSpamList":40,"isMalware":40,"company":41},"6a452308a20f867c8ba8e759","Amtrak","Amtrak Customer Support Data Incident (2026)","amtrak","amtrak.com","2026-04-03T00:00:00.000Z","2026-04-17T04:54:48.000Z",null,"2026-09-19T17:08:19.658Z","2026-07-29T11:13:00.741Z","Authenticated rail customer-support corpus","https:\u002F\u002Fwww.amtrak.com\u002F",[17,19,20],"https:\u002F\u002Fdatabreach.com\u002Fbreach\u002Famtrak-2026","https:\u002F\u002Fwww.breachsense.com\u002Fbreaches\u002Famtrak-data-breach\u002F",2147679,"known","email_identifiers","en",[24,26],"tr",{"en":28,"tr":29},{"slug":9},{"slug":9},"Critical",[32,33,34,35],"Email addresses","Names","Physical addresses","Support tickets","\u003Cp>\u003Cstrong>The 2026 Amtrak customer-support data incident\u003C\u002Fstrong> is a support-data corpus catalogued with a structured date of April 3, 2026, and 2,147,679 unique emails. Its four reported classes are emails, names, physical addresses, and support tickets.\u003C\u002Fp>\u003Cp>The 2,147,679 figure is not unique people, passengers, active accounts, support requests, tickets, or rows containing every field together. Passwords, payments or cards, phones, and complete ticket or travel histories are not classes in this record. There is no local searchable person-level corpus.\u003C\u002Fp>\u003Cp>A record does not establish identity, Amtrak customer or passenger status, a particular ticket, route, delay, refund, or baggage event, address or email ownership, field co-occurrence, password or payment data, account takeover, or misuse.\u003C\u002Fp>\u003Cp>A refund, delay, baggage, ticket-change, or payment request quoting correct support or travel details should be verified through an independent official Amtrak channel without using links in the message.\u003C\u002Fp>","Amtrak Customer Support Data Incident (2026) (2.1 Million Email Identifiers)","Amtrak Customer Support Data Incident (2026). 2.1 Million email identifiers are reported. Reported data: Email addresses, Names, Physical addresses. Review…","\u002Fuploads\u002Flogo\u002Famtrak_com.webp",false,{"name":7,"sector":42,"country":43,"website":10,"websiteArchiveUrl":44,"websiteStatus":44,"websiteCheckedAt":13},"Travel","United States",""]