DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteSEC 8-KState AGConfirmed11 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 11 filings

Tri Counties Bank — February 2023 breach

Clustered 11 filings across 9 jurisdictions · filing window Mar 19, 2023 → Nov 22, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

74,385

First → last filing

Mar 19, 2023 → Nov 22, 2023

Merge confidence

100%

incident inc_ddd7feb095e44378 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Feb 7, 2023–Feb 8, 2023, discovered Feb 7, 2023 — the first regulatory filing landed 247 days later (flagged late). 74,385 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 247-day schedule across 10 filings beginning Mar 19, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
247days

Discovered → first regulatory filing

Discovery variance
244days

Range of discovered_at dates across filings

Leak precedence
206days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
247days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksCalifornia✗ CA 60-day late · 247dLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✓ ME AG ≤30d · 3dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 7, 2023breach begins
Feb 7, 2023discovered · members disagree
notification delay · 247 days
Oct 12, 2023first filing
Nov 22, 2023most 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. MAR 19Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. OCT 12ME AGME AG noticestates nationwide total 8,697+206d
  3. OCT 12CA AGCA AG noticeno count stated+206d
  4. OCT 12MT AGMT AG notice91 MT residents+206d
  5. OCT 12IN AGIN AG noticestates nationwide total 8,697+206d
  6. OCT 12MA AGMA AG notice53 MA residents+206d
  7. OCT 13SEC 8-KSEC 8-K noticeno count stated+207d
  8. NOV 22CA AGCA AG noticeno count stated+247d
  9. NOV 22NH AGNH AG noticeno count stated+247d
  10. NOV 22VT AGVT AG noticeno count stated+247d
  11. NOV 22ME AGME AG noticemost recent · states nationwide total 74,385+247d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 7, 2023
ME AG
Discovered
Feb 7, 2023CA AG + MT AG + SEC 8-K +2Oct 9, 2023ME AGfilings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PII
ME AG + CA AG + MT AG +4
Attack vector
Unauthorized Access
ME 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)

74,385

Sum of filed state slices

173· 0.2% of stated

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

US74,385
MT91
MA53
ME24
IN5

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

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

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

247 days

Cadence

~1 / 24.7d

vs. multi-state median

30.9× 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.