HackingTransportation & LogisticsTransportationStolen CredentialsCustomer Data InvolvedCredentialsIdentity (basic)LowResolved

Amtrak

bd_00fb63d5aaac710b · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 24, 2020

Filed

Nov 5, 2020

To disclose

15 weeks

Affected

72state residents only

Linked

5 filings

Confidence

66%

Full breach record for Amtrak →4 incidents on file

Amtrak notified Montana AG of a July 24, 2020 incident where unauthorized third parties accessed Amtrak Guest Rewards accounts using compromised usernames and passwords. No financial or SSN data was compromised. Amtrak reset passwords, engaged cybersecurity experts, and offered one year of Experian IdentityWorks. The incident is resolved.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 15 weeks / 104 days

Jul 24, 2020

Discovered

Nov 5, 2020

Filed

This filing is one of 5 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Maine State AGbd_3b6e36d60242cb512020-11-04 · +1dCandidate
California State AGbd_970e71f598be3db92020-11-04 · +1dVerified
Washington State AGbd_f2ad5e3d1d8ef1412020-11-04 · +1dVerified
New Hampshire State AGbd_3dca81f577463bc32020-11-09 · +4dVerified

Name: Amtrak
norm: amtrak
Domain: amtrak.com

Name: Amtrak
norm: amtrak
Domain: amtrak.com
Industry: Transportation & Logisticsllm

Discovered: Jul 24, 2020
Materiality determined: —
Notification sent: Nov 5, 2020
Affected individuals: 72state-resident count only
Data types: CredentialsIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Initial access: valid_credentials

During the incident: Engaged outside cybersecurity experts to assist with its response
Reset the passwords for potentially affected accounts
Implemented additional safeguards
Offering a complimentary one-year membership of Experian’s IdentityWorks
Changes made: Implemented additional safeguards
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 15 weeks(104 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Maine State AGNov 4 · first

California State AGNov 4 · first

Washington State AGNov 4 · first

Montana State AG+1d · this page

New Hampshire State AG+5d

Pattern: first filing Nov 4 (ME), last Nov 9 (NH) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/amtrakSamp.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 5, 2020
Raw hash: 56031b60f23d354947a9e623d5a3200dbb0c67ffc41f799560e4e69a9410c3ad

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityAmtrak

Victim entityAmtrak

Incidentdiscovered Jul 24, 2020

Stated responseEngaged outside cybersecurity experts to assist with its response

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov