DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed8 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0pcritical sensitivity
Merged incident · 8 records

Cierant — October 2024 breach

Clustered 8 records across 6 jurisdictions: 7 filings and 1 leak-site claim · filing window Jul 3, 2025 → Jul 8, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

6

Affected · reported

232,506

First → last dated filing

Jul 3, 2025 → Jul 8, 2025

Merge confidence

100%

incident inc_31261bf3109947b9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Oct 22, 2024–Dec 9, 2024, discovered Dec 10, 2024. 232,506 individuals reported across the linked filings. Data reported: Government ID, Minor, Health (basic), and 3 more. Notifications rolled out on a 5-day schedule across 6 dated filings beginning Jul 3, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
146days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 205dTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Oct 22, 2024breach begins
Dec 10, 2024discovered · members disagree
Jul 3, 2025first dated filing
Jul 8, 2025most 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. FEB 1Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  2. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 3HHS OCRHHS OCR noticestates nationwide total 232,506+151d
  4. JUL 7WA AGWA AG notice902 WA residents+155d
  5. JUL 7MT AGMT AG notice84 MT residents+155d
  6. JUL 7CA AGCA AG noticeno count stated+155d
  7. JUL 7WA AGWA AG notice987 WA residents+155d
  8. JUL 8TX AGTX AG noticemost recent · states nationwide total 232,506+156d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 22, 2024 – Dec 9, 2024
WA AG
Discovered
Dec 10, 2024IL AG + WA AG + MT AG +1May 5, 2025TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
IL AG + HHS OCR + WA AG +3
Attack vector
Unauthorized Access
HHS OCR

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)

232,506

Sum of filed state slices

2,647· 1.1% of stated

99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US232,506
TX1,576
WA987
MT84

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 filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

5 days

Cadence

~1 / 1d

vs. multi-state median

1.2× faster

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.