GLOBALMalwareProfessional ServicesProfessional ServicesRansomwareCl0pRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh
Maximus
bd_08c05ac3d136140d · schema v1 · pii pii-v1
Full breach record for Maximus →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Group activity: Business ServicesDiscovered: 2023-07-26
Source: Ransomware.live
Post text · scraped from the leak site
Moving people forward - Maximus
This filing is one of 3 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- bd_d4deac1eb085d27aWashington State AGfiled 2023-08-25(30d gap)Verified
- bd_5312733f463970a3Idaho State AGfiled 2024-01-10(168d gap)Verified by operator
Source provenance
- Source URL
- https://www.ransomware.live/id/TUFYSU1VUy5DT01AY2xvcA==
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jul 26, 2023
- Raw hash
- f80710fa24525dcc4e76bf3f7d22da5855b9d3874521e388fb80e7bbbaafa986
Reporting entity
- Name
- clopnorm: cl0p
Victim entity
- Name
- Maximusnorm: maximus
- Domain
- maximus.com
- Industry
- Professional Services
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· cl0p
- Threat actor
- Cl0pExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.