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 →
incident inc_ee8218ee9803440e · merged by human · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JAN 1IL AGIL AG noticefirst filing · no count statedoperator-confirmedday 0
- JUN 28IN AGIN AG notice1 IN residentsauto-linked+178d
- JUL 26Leak sitecl0p postattacker claim · unverified+206d
- JUL 26SEC 8-KSEC 8-K noticestates nationwide total 8,000,000operator-confirmed+206d
- JUL 28MT AGMT AG notice14,769 MT residentsoperator-confirmed+208d
- JUL 28ID AGID AG notice4,852 ID residentsoperator-confirmed+208d
- AUG 4HHS OCRHHS OCR noticestates nationwide total 9,179,390auto-linked+215d
- AUG 18CA AGCA AG noticeno count statedauto-linked+229d
- AUG 24IN AGIN AG notice40,470 IN residentsoperator-confirmed+235d
- AUG 25NH AGNH AG notice6,376 NH residentsoperator-confirmed+236d
- AUG 25VT AGVT AG noticeno count statedoperator-confirmed+236d
- AUG 25DE AGDE AG noticeno count statedoperator-confirmed+236d
- AUG 25WA AGWA AG notice70,847 WA residentsoperator-confirmed+236d
- AUG 26HI AGHI AG notice2,807 HI residentsoperator-confirmed+237d
- AUG 29OR AGOR AG noticeno count statedoperator-confirmed+240d
- AUG 29SC AGSC AG notice77,405 SC residentsauto-linked+240d
- JAN 10ID AGID AG noticemost recent · 20,513 affectedoperator-confirmed+374d
- 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.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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.