Employee answered a vishing call; unauthorized party accessed CSX Microsoft 365 and acquired files 2026-05-29 to 2026-06-09; detected via unusual-activity alert in June; on 2026-08-26 CSX determined files held personal information.
Other explanations considered: Aggregator lag, not a new incident.
- 2026-05-29 to 2026-06-09 · DETEmployee answered a vishing call; unauthorized party accessed CSX Microsoft 365 and acquired files 2026-05-29 to 2026-06-09; detected via unusual-activity alert in June; on 2026-08-26 CSX determined files held personal information.Source
- 2026-05-29 to 2026-06-09 · DISIn-window resurfacing: security news roundup of 2026-11-03 presents the CSX breach as fresh news. Date-discipline hazard: this is the May-June 2026 intrusion notified 2026-10-20, not a new event. No operational impact on rail service reported at any point.Source
- Oct 20 · DISAG/consumer-agency notices: New Hampshire (57 residents, filing dated 2026-10-20), Massachusetts OCABR (434), Vermont (count not shown); Maine AG portal lists CSX (page 403 to fetcher). Data: names, SSNs, driver's license numbers, bank account and routing...Source
- Oct 20 · REM24 months credit monitoring via Epiq Privacy Solutions ID; dedicated incident line 888-619-1563.Source