Clustered 2 filings across 1 jurisdiction · filing window Jul 14, 2023 → Jul 20, 2023. View entity profile → Other incidents for this victim →
incident inc_fefc8f590ee943f4 · merge_method deterministic · confidence 93%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Financial account · Financial credentials
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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 24, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 1, 2023
Reported by MAINE AG filings
Maersk Line, Limited reported an external system breach that was discovered on June 1, 2023. The breach occurred on May 24, 2023, and affected 3 Maine residents. The compromised information included names and financial account numbers or credit/debit card numbers with their security codes. Affected individuals were notified on June 5, 2023, and offered identity theft protection services.
Affected (this filing): 3
Maersk Line, Limited experienced an external system breach on May 24, 2023, which was discovered on June 1, 2023. The breach affected 3 Maine residents, compromising their names in combination with financial account or credit/debit card numbers and their respective security codes or PINs. The company notified the affected individuals electronically on June 5, 2023, and offered one year of identity theft protection services.
Affected (this filing): 3
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.