GLOBALClaimed by StormousFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Mar 28, 2022bd_807d5f99a42595c7
Clustered 3 filings across 3 jurisdictions · filing window Mar 28, 2022 → Apr 28, 2022. View entity profile → Other incidents for this victim →
incident inc_1532ef088c564f9d · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Government ID
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 12, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 12, 2022
Reported by NEW HAMPSHIRE AG filing
Apr 12, 2022
Reported by MAINE AG filing
Smith Transport, Inc. reported a data breach affecting 50 Maine residents following an external system breach discovered on April 12, 2022. The incident, which occurred on February 12, 2022, compromised names combined with driver's license or non-driver identification card numbers. The company notified affected individuals on April 27, 2022 and offered identity theft protection services through IDX.
Affected (this filing): 50
Smith Transport, Inc. notified the New Hampshire Attorney General of a data security incident discovered on February 12, 2022. The breach impacted the personal information (name, SSN, DOB, driver's license) of 36 New Hampshire residents. Smith Transport engaged forensic experts, notified the FBI, and provided complimentary identity protection services through IDX.
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.
Affected (this filing): 36