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

TRISTAR Insurance Group — November 2022 breach

Clustered 10 filings across 8 jurisdictions · filing window Dec 11, 2023 → Mar 18, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

35,120

First → last dated filing

Dec 11, 2023 → Mar 18, 2024

Merge confidence

100%

incident inc_90944b89dc4147b1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Nov 4, 2022–Nov 9, 2022, discovered Nov 4, 2022 — the first regulatory filing landed 402 days later. 35,120 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 98-day schedule across 9 dated filings beginning Dec 11, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
402days

Discovered → first regulatory filing

Discovery variance
377days

Range of discovered_at dates across filings

Filing span
98days

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 clocksMaine⏱ ME AG >30d · 77dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 4, 2022breach begins
Nov 4, 2022discovered · members disagree
notification delay · 402 days
Dec 11, 2023first dated filing
Mar 18, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. DEC 11CA AGCA AG noticefirst filing · no count statedday 0
  2. DEC 11MA AGMA AG notice14 MA residentsday 0
  3. JAN 19MT AGMT AG notice38 MT residents+39d
  4. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  5. FEB 1ME AGME AG noticestates nationwide total 35,120+52d
  6. FEB 1IN AGIN AG noticestates nationwide total 35,120+52d
  7. FEB 1NH AGNH AG notice27 NH residents+52d
  8. FEB 1CA AGCA AG noticeno count stated+52d
  9. FEB 2SC AGSC AG notice1,488 SC residents+53d
  10. MAR 18NH AGNH AG noticemost recent · 2 NH residents+98d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 4, 2022 – Nov 9, 2022
CA AG
Discovered
Nov 4, 2022IL AGNov 10, 2022CA AG + MT AG + NH AG +1Nov 16, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + MT AG + ME AG +3
Attack vector
Unauthorized Access
CA 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)

35,120

Sum of filed state slices

2,106· 6.0% of stated

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

US35,120
SC1,488
IN499
ME40
MT38
NH27
MA14

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

98 days

Cadence

~1 / 12.3d

vs. multi-state median

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