Clustered 3 filings across 3 jurisdictions · filing window Dec 9, 2022 → Jan 12, 2023. View entity profile → Other incidents for this victim →
incident inc_1646b9fc06e64af5 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
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.
ME NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 31, 2022 → Sep 3, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 11, 2022
Reported by NEW HAMPSHIRE AG, VERMONT AG filings
Nov 28, 2022
Reported by MAINE AG filing
SEACOR Holdings Inc. notified the NH Attorney General of a cybersecurity incident where an unauthorized actor accessed server folders between Aug 31 and Sep 3, 2022. The breach affected one NH resident's name, SSN, and/or driver's license. SEACOR engaged a cybersecurity firm, contained the incident, and offered one year of credit monitoring.
Affected (this filing): 1
SEACOR Holdings Inc. notified consumers of a security incident where an unauthorized actor accessed server folders between August 31 and September 3, 2022. The incident exposed names, passport numbers, merchant mariner numbers, and health information. SEACOR engaged a cybersecurity firm and implemented enhanced security tools.
SEACOR Holdings Inc. reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred between August 31, 2022, and September 3, 2022. The breach was discovered on November 28, 2022. The incident affected 5 Maine residents, and involved the compromise of names and Social Security numbers. The company began notifying affected individuals on January 12, 2023, and offered a one-year membership to credit monitoring and identity theft protection services.
Affected (this filing): 5
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.