DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Adams Bank & Trust — May 2023 breach

Clustered 6 filings across 5 jurisdictions · filing window Nov 15, 2023 → Mar 1, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

23,819

First → last filing

Nov 15, 2023 → Mar 1, 2024

Merge confidence

100%

incident inc_2adee9f925924fbe · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion May 15, 2023–May 16, 2023, discovered May 16, 2023 — the first regulatory filing landed 183 days later (flagged late). 23,819 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 107-day schedule across 6 filings beginning Nov 15, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
183days

Discovered → first regulatory filing

Discovery variance
129days

Range of discovered_at dates across filings

Filing span
107days

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.

Regulatory clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 54dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 15, 2023breach begins
May 16, 2023discovered · members disagree
notification delay · 183 days
Nov 15, 2023first filing
Mar 1, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. NOV 15VT AGVT AG noticefirst filing · no count statedday 0
  2. NOV 15MT AGMT AG notice28 MT residentsday 0
  3. NOV 15MA AGMA AG notice2 MA residentsday 0
  4. NOV 15ME AGME AG noticestates nationwide total 23,819day 0
  5. NOV 15NH AGNH AG noticeno count statedday 0
  6. MAR 1NH AGNH AG noticemost recent · 6 NH residents+107d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 15, 2023 – May 16, 2023
VT AG
Discovered
May 16, 2023VT AG + MT AG + NH AGSep 22, 2023ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
VT AG + MT AG + NH AG +2
Attack vector
Unauthorized Access
VT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

23,819

Sum of filed state slices

37· 0.2% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US23,819
MT28
NH6
MA2
ME1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

107 days

Cadence

~1 / 21.4d

vs. multi-state median

13.4× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.