Confirmed breach. Intrusion Mar 14, 2022, discovered Mar 23, 2022 — the first regulatory filing landed 70 days later. 4,524 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine⏱ ME AG >30d · 70dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
4,524
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME NH
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 14, 2022
When the intrusion reportedly occurred, per the linked filings
Big M Transportation, Inc. experienced an external system breach on March 14, 2022, discovered on March 23, 2022. The incident compromised the names and Social Security numbers of 4,524 individuals. The company began notifying affected individuals on June 1, 2022, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 4,524
ME AG >30d · 70dME resident >60d · 70d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
State of New Hampshire Attorney General breach notification filed by Big M Transportation, Inc. on June 6, 2022. The provided attachment content is empty; no specific breach details, dates, or data types are available for extraction.
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.