DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRSEC 8-KState AGConfirmed17 filings · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 17 filings

MAXIMUS, Inc. — May 2023 breach

Clustered 17 filings across 15 jurisdictions · filing window Jan 1, 2023 → Jan 10, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

14

Affected · reported

9,179,390

First → last filing

Jan 1, 2023 → Jan 10, 2024

Merge confidence

100%

incident inc_ee8218ee9803440e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 27, 2023–May 31, 2023, discovered May 27, 2023. 9,179,390 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 2 more. Notifications rolled out on a 374-day schedule across 16 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
4days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 206d

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dWashington⏱ WA AG >30dLeak gap⏱ Leak >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 27, 2023discovered · members disagree
Jan 1, 2023first filing
Jan 10, 2024most 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 28IN AGIN AG notice1 IN residents+178d
  3. JUL 26Leak sitecl0p postattacker claim · unverified+206d
  4. JUL 26SEC 8-KSEC 8-K noticestates nationwide total 8,000,000+206d
  5. JUL 28MT AGMT AG notice14,769 MT residents+208d
  6. JUL 28ID AGID AG notice4,852 ID residents+208d
  7. AUG 4HHS OCRHHS OCR noticestates nationwide total 9,179,390+215d
  8. AUG 18CA AGCA AG noticeno count stated+229d
  9. AUG 24IN AGIN AG notice40,470 IN residents+235d
  10. AUG 25NH AGNH AG notice6,376 NH residents+236d
  11. AUG 25VT AGVT AG noticeno count stated+236d
  12. AUG 25DE AGDE AG noticeno count stated+236d
  13. AUG 25WA AGWA AG notice70,847 WA residents+236d
  14. AUG 26HI AGHI AG notice2,807 HI residents+237d
  15. AUG 29OR AGOR AG noticeno count stated+240d
  16. AUG 29SC AGSC AG notice77,405 SC residents+240d
  17. JAN 10ID AGID AG noticemost recent · 20,513 affected+374d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023 – May 31, 2023
MT AG
Discovered
May 27, 2023IL AGMay 30, 2023MT AG + ID AG + CA AG +6May 31, 2023OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + MT AG + CA AG +8
Attack vector
Third-Party / Supply Chain
SEC 8-K

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)

9,179,390

Sum of filed state slices

233,187· 2.5% of stated

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

US9,179,390
SC77,405
WA70,847
IN40,470
ID20,513
MT14,769
NH6,376
HI2,807

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing15 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

374 days

Cadence

~1 / 23.4d

vs. multi-state median

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