GLOBALClaimed by StormousFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Apr 25, 2022bd_3495efb65792b9f1
Clustered 3 filings across 3 jurisdictions · filing window Apr 25, 2022 → Jun 10, 2022. View entity profile → Other incidents for this victim →
incident inc_e1ab4d11df0f4d3b · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Government ID · Identity (basic)
CA ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 29, 2020
When the intrusion reportedly occurred, per the linked filings
Feb 25, 2022
Reported by CALIFORNIA AG filing
May 13, 2022
Reported by MAINE AG filing
An external system breach at Danaher Corporation resulted in the compromise of names and Social Security numbers. The breach occurred on December 29, 2020, and was discovered on May 13, 2022. The company notified the 13 affected Maine residents on June 13, 2022, and offered 24 months of identity theft protection services through Experian.
Affected (this filing): 13
Danaher Corporation reported a data breach involving its third-party vendor, Aon PLC. An unauthorized third party accessed Aon systems between December 29, 2020, and February 26, 2022, obtaining documents containing personal information including names and Social Security numbers. Aon notified law enforcement (FBI), engaged forensic investigators, and offered 24 months of credit monitoring via Experian. The breach was reported to the California AG on June 13, 2022.
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.