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

MAXIMUS, Inc. — May 2023 breach

Clustered 18 records across 15 jurisdictions: 17 filings and 1 leak-site claim · filing window Jun 28, 2023 → Jan 10, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

18 records

States

14

Affected · reported

9,179,390

First → last dated filing

Jun 28, 2023 → Jan 10, 2024

Merge confidence

100%

incident inc_ee8218ee9803440e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 17 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 3 more. Notifications rolled out on a 196-day schedule across 16 dated filings beginning Jun 28, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
4days

Range of discovered_at dates across filings

Filing span
196days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay

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

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 27, 2023discovered · members disagree
Jun 28, 2023first dated filing
Jan 10, 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 and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUN 28IN AGIN AG noticefirst filing · 1 IN residentsday 0
  3. JUL 26Leak sitecl0p postattacker claim · unverified+28d
  4. JUL 26SEC 8-KSEC 8-K noticestates nationwide total 8,000,000+28d
  5. JUL 28MA AGMA AG notice58,800 MA residents+30d
  6. JUL 28ID AGID AG notice4,852 ID residents+30d
  7. JUL 28MT AGMT AG notice14,769 MT residents+30d
  8. AUG 4HHS OCRHHS OCR noticestates nationwide total 9,179,390+37d
  9. AUG 18CA AGCA AG noticeno count stated+51d
  10. AUG 24IN AGIN AG notice40,470 IN residents+57d
  11. AUG 25NH AGNH AG notice6,376 NH residents+58d
  12. AUG 25VT AGVT AG noticeno count stated+58d
  13. AUG 25DE AGDE AG noticeno count stated+58d
  14. AUG 25WA AGWA AG notice70,847 WA residents+58d
  15. AUG 26HI AGHI AG notice2,807 HI residents+59d
  16. AUG 29OR AGOR AG noticeno count stated+62d
  17. AUG 29SC AGSC AG notice77,405 SC residents+62d
  18. JAN 10ID AGID AG noticemost recent · 20,513 affected+196d
  19. 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
ID AG
Discovered
May 27, 2023IL AGMay 30, 2023ID AG + MT AG + CA AG +6May 31, 2023OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + MT AG + CA AG +9
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

291,987· 3.2% 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
MA58,800
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 filing16 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 Sep 28, 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

196 days

Cadence

~1 / 13.1d

vs. multi-state median

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