Confirmed breach. Intrusion Feb 20, 2024, discovered Mar 21, 2024 — the first regulatory filing landed 29 days later. 3,370 individuals reported across the linked filings.
incident inc_62c473526765467d · merge_method human · confidence 100%
Litigation Timing
Notification delay
29days
Discovered → first regulatory filing
Leak precedence
32days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsnatch
32days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Affected (total reported)
3,370
Data types
—
Jurisdictions
2
ME
Linked filings
2
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 20, 2024
When the intrusion reportedly occurred, per the linked filings
Butler, Lavanceau & Sober, LLC is a certified public accounting firm centrally located in Columbia, Maryland. Our seasoned accountants have over 200 years of combined expertise and are ready to meet your individual and business accounting, tax, and consulting needs.
Breach discovered
Mar 21, 2024
Reported by MAINE AG filing
🦞Maine State AGMost recentLeaked → filing gap · 32dlinked via operator-confirmed · 100%
Butler, Lavanceau, & Sober, LLC, a financial services company, reported an external system breach that occurred on February 20, 2024, and was discovered on March 21, 2024. The incident affected 3,370 individuals, exposing their names and driver's license or non-driver ID numbers. The company began notifying affected individuals on April 17, 2024, and offered 12 months of identity protection services through Identity Defense.
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.