Confirmed breach. Intrusion Apr 13, 2025–Apr 15, 2025, discovered Apr 15, 2025 — the first regulatory filing landed 134 days later (flagged late). 43,874 individuals reported across the linked filings.
Regulatory clocksWashington✗ WA AG >90dTexas✗ TX AG >30dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
43,874
Data types
—
Jurisdictions
8
CA IN MT NH OR TX VT WA
1days
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Linked filings
8
all State AG
Affected residents by state
per-filing reported counts
OR40,018
IN40,017
WA3,267
TX559
MT26
NH3
VT1
State AGs report only their own residents; bars show per-filing counts.
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
8 filings across 8 jurisdictions · Aug 27, 2025 – Aug 28, 2025 · 3 milestones
Breach window
Apr 13, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Apr 15, 2025
Reported by WASHINGTON AG, NEW HAMPSHIRE AG filings
104 days
Breach discoveredconflicts with Apr 15, 2025AG web form
Jul 28, 2025
Reported by OREGON AG, TEXAS AG filings
30 days
8 State AG filingsAug 27, 2025 – Aug 28, 2025ExpandCollapse
ORVTMTCAWAINTXNH
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Lasership Inc. dba OnTrac Final Mile (“OnTrac”) reported a data breach to the Oregon Attorney General. The breach was reported on 2025-08-27. The breach occurred during 4/13/2025 - 4/15/2025. The breach was discovered on 7/28/2025. 40,018 individuals were affected. Notice was sent on 8/27/2025.
Affected (this filing): 40,018
OR AG ≤45d
🍁Vermont State AGlinked via multistate filing link · 100%
Lasership Inc. dba OnTrac Final Mile notified consumers of a data breach involving unauthorized access to email accounts. The incident impacted at least one Vermont resident and potentially others across multiple jurisdictions. Affected data included names and Social Security numbers. The company is offering 12 months of credit monitoring services.
Affected (this filing): 1
🦬Montana State AGlinked via multistate filing link · 100%
Lasership, Inc. dba OnTrac Final Mile reported a data breach to the Montana Attorney General. The breach was reported on 2025-08-27. The breach occurred from 04/13/2025 to 04/15/2025. 26 Montana residents were affected.
Affected (this filing): 26
🐻California State AGlinked via multistate filing link · 100%
Lasership Inc. dba OnTrac Final Mile reported a data breach to the California Attorney General. The incident occurred between April 13, 2025, and April 15, 2025. The breach affected residents of California, Maryland, New Mexico, New York, North Carolina, Rhode Island, and Washington, D.C. The compromised data likely included names, addresses, and Social Security numbers, as indicated by the offer of credit monitoring and fraud assistance services. The specific cause of the breach and the number of affected individuals were not disclosed in the provided notification sample.
🌲Washington State AGlinked via multistate filing link · 100%
Lasership Inc. dba OnTrac Final Mile (“OnTrac”), a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-04-15 and filed notice on 2025-08-27. 3,267 Washington residents were affected. 134 days elapsed between awareness and notification. 2 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 3,267
WA AG >90d
🏎️Indiana State AGlinked via multistate filing link · 100%
Lasership Inc dba OnTrac Final Mile reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-13 and was reported on 2025-08-27. 75 Indiana residents were affected. 40,017 individuals affected in total.
Affected (this filing): 40,017
⭐Texas State AGlinked via multistate filing link · 100%
Lasership Inc. dba OnTrac Final Mile (“OnTrac”) based in Chantilly, Virginia, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-07-28 and reported on 2025-08-28. 559 Texas residents were affected. 40,018 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Medical Information. Consumers were notified via U.S. Mail.
Affected (this filing): 559
TX AG >30d
⛰️New Hampshire State AGlinked via multistate filing link · 100%
Lasership, Inc. (dba OnTrac Final Mile) notified the New Hampshire Attorney General of a data security incident affecting 3 New Hampshire residents. Unauthorized access to OnTrac's network occurred between April 13 and 15, 2025. The incident involved the potential access of names and Social Security numbers. OnTrac engaged forensic specialists, notified law enforcement, and implemented additional security measures. Affected individuals were notified on August 27, 2025, and offered 12 months of credit monitoring.