Aon
bd_d4e9fb69d737f7a6 · schema v1 · pii pii-v1
Full breach record for Aon →12 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Dispossessor 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.
Source: Ransomware.live
Post text · scraped from the leak site
aon.com
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 3, 2022
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Maine State AGbd_83344b1fed7fdb7a2022-07-01 · +2dCandidate
- Maine State AGbd_ee7cfc9886fcd7132022-06-24 · +9dCandidate
- New Hampshire State AGbd_5ba6400246ccb57f2022-06-13 · +20dVerified by operator
- Montana State AGbd_f3bea3092e6d8ecc2022-06-13 · +20dVerified by operator
Show 6 more filings ↓Show fewer ↑up to 38d gap
- New Hampshire State AGbd_bed97e68b6fb0b6c2022-05-31 · +33dVerified by operator
- Indiana State AGbd_fde32f8598ecaa8b2022-05-27 · +37dVerified
- HHS OCRbd_1659c519cbbc91942022-05-26 · +38dVerified by operator
- Oregon State AGbd_a34b45e6fa897e082022-05-26 · +38dVerified
- California State AGbd_a3a4b3bd3ddac8fc2022-05-26 · +38dVerified
- Maine State AGbd_bdef13158191852d2022-05-26 · +38dCandidate
Showing first 10 of 13 linked disclosures.
Filing propagation · 10 filings · 7 states
View merged incident ↗Pattern: first filing May 26 (IL), last Jul 1 (ME) — a 36-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 13 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
dispossessor
According to ransomware.live, This is not a ransomware group but a data broker