DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed13 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 13 filings

Imagine360 — January 2023 breach

Clustered 13 filings across 10 jurisdictions · filing window Mar 24, 2023 → Jul 21, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

9

Affected · reported

132,807

First → last filing

Mar 24, 2023 → Jul 21, 2023

Merge confidence

100%

incident inc_1cf812a03e734e2f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Jan 28, 2023–Jan 30, 2023, discovered Jan 30, 2023 — the first regulatory filing landed 151 days later (flagged late). 132,807 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 3 more. Notifications rolled out on a 119-day schedule across 12 filings beginning Mar 24, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
151days

Discovered → first regulatory filing

Discovery variance
122days

Range of discovered_at dates across filings

Leak precedence
98days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
119days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 151dWashington✗ WA AG >90dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 50dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 28, 2023breach begins
Jan 30, 2023discovered · members disagree
notification delay · 151 days
Jun 30, 2023first filing
Jul 21, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 24Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. JUN 30VT AGVT AG noticeno count stated+98d
  3. JUN 30ME AGME AG noticestates nationwide total 112,611+98d
  4. JUN 30MA AGMA AG notice257 MA residents+98d
  5. JUN 30CA AGCA AG noticeno count stated+98d
  6. JUN 30WA AGWA AG notice1,478 WA residents+98d
  7. JUN 30HHS OCRHHS OCR noticestates nationwide total 132,807+98d
  8. JUN 30OR AGOR AG noticestates nationwide total 112,611+98d
  9. JUL 3SC AGSC AG notice2,485 SC residents+101d
  10. JUL 5NH AGNH AG notice82 NH residents+103d
  11. JUL 21NH AGNH AG noticeno count stated+119d
  12. JUL 21ME AGME AG noticestates nationwide total 132,651+119d
  13. JUL 21CA AGCA AG noticemost recent · no count stated+119d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 28, 2023 – Jan 30, 2023
VT AG
Discovered
Jan 30, 2023VT AG + CA AG + WA AG +2Jun 1, 2023ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + ME AG + CA AG +5
Attack vector
Third-Party / Supply Chain
VT AG

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)

132,807

Sum of filed state slices

4,562· 3.4% of stated

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

US132,807
SC2,485
WA1,478
ME260
MA257
NH82

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 filing12 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 22, 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

119 days

Cadence

~1 / 9.9d

vs. multi-state median

14.9× slower

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.