DisclosureLens
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddragonforcehigh sensitivity
Merged incident · 6 filings

Statesman Business Advisors — March 2025 breach

Clustered 6 filings across 5 jurisdictions · filing window Apr 4, 2025 Aug 22, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

2,273

First → last filing

Apr 4, 2025 Aug 22, 2025

Merge confidence

100%

incident inc_9257b97a3ad64c00 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Mar 26, 2025–Apr 4, 2025, discovered Jun 20, 2025 — the first regulatory filing landed 60 days later (flagged late). 2,273 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 140-day schedule across 4 filings beginning Apr 4, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
137days 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
140days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksTexas TX AG >30dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 26, 2025breach begins
Jun 20, 2025discovered
notification delay · 60 days
Aug 19, 2025first filing
Aug 22, 2025most 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. APR 4Leak sitedragonforce postfirst filing · attacker claim · unverifiedday 0
  2. APR 11Leak sitedragonforce postattacker claim · unverified+7d
  3. AUG 19VT AGVT AG noticeno count stated+137d
  4. AUG 19IN AGIN AG noticestates nationwide total 2,273+137d
  5. AUG 20MT AGMT AG notice3 MT residents+138d
  6. AUG 22TX AGTX AG noticemost recent · states nationwide total 2,273+140d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 26, 2025Apr 4, 2025
VT AG
Discovered
Jun 20, 2025· 86d undetected
VT AG + MT AG + TX AG
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + MT AG + TX AG
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)

2,273

Sum of filed state slices

2,016· 88.7% of stated

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

US2,273
TX2,012
MT3
IN1

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

140 days

Cadence

~1 / 28d

vs. multi-state median

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