DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 11 filings

Beacon Mutual Insurance — January 2026 breach

Clustered 11 filings across 10 jurisdictions · filing window Jan 14, 2026 → May 19, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

162,439

First → last filing

Jan 14, 2026 → May 19, 2026

Merge confidence

100%

incident inc_6dec00df1e7a4db4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jan 7, 2026–Jan 14, 2026, discovered Jan 14, 2026 — the first regulatory filing landed 124 days later (flagged late). 162,439 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 125-day schedule across 9 filings beginning Jan 14, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
124days

Discovered → first regulatory filing

Discovery variance
107days

Range of discovered_at dates across filings

Leak precedence
124days 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
125days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 30-day late · 124dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 7, 2026breach begins
Jan 14, 2026discovered · members disagree
notification delay · 124 days
May 18, 2026first filing
May 19, 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. JAN 14Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. JAN 31Leak siteinc_ransom postattacker claim · unverified+17d
  3. MAY 18MT AGMT AG notice35 MT residents+124d
  4. MAY 18VT AGVT AG notice195 VT residents+124d
  5. MAY 18CA AGCA AG noticeno count stated+124d
  6. MAY 18IN AGIN AG noticestates nationwide total 162,439+124d
  7. MAY 18NE AGNE AG notice26 NE residents+124d
  8. MAY 18ME AGME AG notice607 ME residents+124d
  9. MAY 18NH AGNH AG notice646 NH residents+124d
  10. MAY 18MA AGMA AG notice11,890 MA residents+124d
  11. MAY 19TX AGTX AG noticemost recent · states nationwide total 162,439+125d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 7, 2026 – Jan 14, 2026
MT AG
Discovered
Jan 14, 2026MT AG + CA AG + NE AG +1May 1, 2026ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + ME AG +5
Attack vector
Unauthorized Access
MT 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)

162,439

Sum of filed state slices

14,131· 8.7% of stated

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

US162,439
MA11,890
NH646
TX612
ME607
VT195
IN120
MT35
NE26

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

125 days

Cadence

~1 / 12.5d

vs. multi-state median

13.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.