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

WILTON REASSURANCE COMPANY — May 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Jun 22, 2023 → Aug 10, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

1,482,490

First → last filing

Jun 22, 2023 → Aug 10, 2023

Merge confidence

100%

incident inc_8950172113634c85 · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe hacking. Intrusion May 29, 2023–May 30, 2023, discovered May 31, 2023 — the first regulatory filing landed 22 days later. 1,482,490 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 3 more. Notifications rolled out on a 49-day schedule across 9 filings beginning Jun 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
22days

Discovered → first regulatory filing

Discovery variance
7days

Range of discovered_at dates across filings

Filing span
49days

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 · 64dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 22 days
Jun 22, 2023first filing
Aug 10, 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. JUN 22CA AGCA AG noticefirst filing · no count statedday 0
  2. JUN 23OR AGOR AG noticestates nationwide total 1,482,490+1d
  3. JUN 23MA AGMA AG notice8,430 MA residents+1d
  4. JUN 23WA AGWA AG notice8,148 WA residents+1d
  5. JUL 10IN AGIN AG noticestates nationwide total 1,433,939+18d
  6. AUG 2MT AGMT AG notice2,441 MT residents+41d
  7. AUG 9CA AGCA AG noticeno count stated+48d
  8. AUG 10NH AGNH AG notice2,013 NH residents+49d
  9. AUG 10ME AGME AG noticemost recent · states nationwide total 1,227,060+49d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023 – May 30, 2023
CA AG
Discovered
May 31, 2023MT AG + CA AGJun 7, 2023OR AG + WA AG + ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
MA AG + WA AG + NH AG +3
Attack vector
Third-Party / Supply Chain· CL0P
WA 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)

1,482,490

Sum of filed state slices

127,291· 8.6% of stated

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

US1,482,490
IN104,027
MA8,430
WA8,148
MT2,441
ME2,232
NH2,013

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

49 days

Cadence

~1 / 6.1d

vs. multi-state median

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

Wilton Reassurance Company data breach (2023) · DisclosureLens