Clustered 3 filings across 3 jurisdictions · filing window Jan 17, 2024 → Feb 16, 2024. View entity profile → Other incidents for this victim →
incident inc_b3b4ddc5889b4b20 · merge_method human · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN ME MT
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Jun 29, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 8, 2023
Reported by MAINE AG filing
Dawson James Securities, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-01-17. The breach occurred from 6/29/2023 to 6/30/2023. 6 Montana residents were affected.
Affected (this filing): 6
Dawson James Securities, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-06-29 and was reported on 2024-01-17. 39 Indiana residents were affected. 4,673 individuals affected in total.
Affected (this filing): 4,673
Dawson James Securities, Inc., a financial services firm, reported an external system breach that occurred on June 29, 2023, and was discovered on December 8, 2023. The incident affected 4,673 individuals, compromising names and financial account numbers with associated security codes or PINs. Notification to affected consumers began on January 17, 2024, and included an offer for 12 months of credit monitoring services.
Affected (this filing): 4,673
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.