Clustered 3 filings across 3 jurisdictions · filing window Oct 18, 2024 → Dec 13, 2024. View entity profile → Other incidents for this victim →
incident inc_97c6b75f6c494a59 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT WA
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.
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
Sep 23, 2024
When the intrusion reportedly occurred, per the linked filings
Sep 23, 2024
Reported by WASHINGTON AG, MAINE AG filings
Falco Sult & Company, PS, a finance sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2024-09-23 and filed notice on 2024-10-18. 1,788 Washington residents were affected. 25 days elapsed between awareness and notification.
Affected (this filing): 1,788
Falco Sult & Company, PS reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-12. The breach occurred on 09/23/2024. 6 Montana residents were affected.
Affected (this filing): 6
Falco Sult & Company, PS, a financial services firm, reported a data breach to the Maine Attorney General's office. The breach, which was discovered on September 23, 2024, was an external system breach (hacking) that occurred on the same day. The breach affected 2 Maine residents. The company provided written notification to affected consumers on December 12, 2024, and offered 12 months of complimentary credit monitoring and identity theft restoration services through Cyberscout.
Affected (this filing): 2
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.