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

HENNESSY ADVISORS, INC. — March 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Feb 1, 2026 → Feb 25, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

12,643

First → last filing

Feb 1, 2026 → Feb 25, 2026

Merge confidence

100%

incident inc_e99dfcc3aaa149b0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Mar 30, 2025, discovered Mar 30, 2025 — the first regulatory filing landed 308 days later (flagged late). 12,643 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Notifications rolled out on a 24-day schedule across 9 filings beginning Feb 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
308days

Discovered → first regulatory filing

Discovery variance
312days

Range of discovered_at dates across filings

Filing span
24days

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 >90d · 331dCalifornia✗ CA 60-day late · 330dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 30, 2025breach begins
Mar 30, 2025discovered · members disagree
notification delay · 308 days
Feb 1, 2026first filing
Feb 25, 2026most 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. FEB 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 23IN AGIN AG noticestates nationwide total 12,643+22d
  3. FEB 23VT AGVT AG noticeno count stated+22d
  4. FEB 23NE AGNE AG noticeno count stated+22d
  5. FEB 24MA AGMA AG noticeno count stated+23d
  6. FEB 24ME AGME AG noticestates nationwide total 12,643+23d
  7. FEB 24CA AGCA AG noticeno count stated+23d
  8. FEB 24NH AGNH AG notice95 NH residents+23d
  9. FEB 25TX AGTX AG noticemost recent · states nationwide total 12,643+24d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 30, 2025
IN AG
Discovered
Mar 30, 2025VT AG + NE AG + ME AG +2Feb 5, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
IL AG + VT AG + ME AG +5
Attack vector
Unauthorized Access
NE 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)

12,643

Sum of filed state slices

1,019· 8.1% of stated

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

US12,643
TX729
IN147
NH95
ME48

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 filing9 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

24 days

Cadence

~1 / 3d

vs. multi-state median

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