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

State of Maine — May 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Nov 9, 2023 → Nov 27, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

1,324,118

First → last filing

Nov 9, 2023 → Nov 27, 2023

Merge confidence

100%

incident inc_4a451e117cbb4b73 · 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 28, 2023–May 29, 2023, discovered May 31, 2023 — the first regulatory filing landed 162 days later (flagged late). 1,324,118 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 18-day schedule across 9 filings beginning Nov 9, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
162days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
18days

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 >90d · 162dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dOregon✗ OR AG >45dSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
May 31, 2023discovered
notification delay · 162 days
Nov 9, 2023first filing
Nov 27, 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. NOV 9ME AGME AG noticefirst filing · states nationwide total 1,324,118day 0
  2. NOV 9MT AGMT AG notice232 MT residentsday 0
  3. NOV 9VT AGVT AG noticeno count statedday 0
  4. NOV 13WA AGWA AG notice2,606 WA residents+4d
  5. NOV 14SC AGSC AG notice1,425 SC residents+5d
  6. NOV 15NH AGNH AG notice8,927 NH residents+6d
  7. NOV 16HHS OCRHHS OCR noticestates nationwide total 376,504+7d
  8. NOV 27OR AGOR AG noticestates nationwide total 1,324,118+18d
  9. NOV 27CA AGCA AG noticemost recent · no count stated+18d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023 – May 29, 2023
ME AG
Discovered
May 31, 2023· 3d undetected
ME AG + MT AG + VT AG +5
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
ME AG + MT AG + VT AG +5
Attack vector
Unauthorized Access
ME 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,324,118

Sum of filed state slices

547,384· 41.3% of stated

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

US1,324,118
ME534,194
NH8,927
WA2,606
SC1,425
MT232

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

18 days

Cadence

~1 / 2.3d

vs. multi-state median

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