GLOBALClaimed by Cl0pFirst sighting
Posted to leak site Jul 26, 2023bd_08c05ac3d136140d
Moving people forward - Maximus
Clustered 3 filings across 3 jurisdictions · filing window Jul 26, 2023 → Jan 10, 2024. View entity profile → Other incidents for this victim →
incident inc_ee8218ee9803440e · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
ID WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 30, 2023
Reported by WASHINGTON AG filing
Moving people forward - Maximus
Maximus, Inc., a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2023-05-30 and filed notice on 2023-08-25. 70,847 Washington residents were affected. 87 days elapsed between awareness and notification. 3 days to identify the breach. 1 days to contain the breach.
Affected (this filing): 70,847
Maximus, Inc. submitted a supplemental data security incident update to the Idaho Attorney General on January 10, 2024, regarding a breach involving MOVEit Transfer. The incident affected 20,513 Idaho residents. Maximus offered 24 months of credit monitoring and identity restoration services through Experian and notified consumer reporting agencies. The investigation is concluded.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 20,513