DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 14 filings

ON Q FINANCIAL, LLC — March 2023 breach

Clustered 14 filings across 12 jurisdictions · filing window Feb 20, 2024 → Apr 11, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

211,650

First → last filing

Feb 20, 2024 → Apr 11, 2024

Merge confidence

100%

incident inc_823b0b4dd0a4403e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings, 1 press report and 2 unverified claims. The filings describe hacking. Intrusion Mar 14, 2023–Feb 22, 2024, discovered Mar 14, 2023 — the first regulatory filing landed 381 days later. 211,650 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 51-day schedule across 11 filings beginning Feb 20, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
381days

Discovered → first regulatory filing

Discovery variance
366days

Range of discovered_at dates across filings

Leak precedence
38days 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
51days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 14, 2023breach begins
Mar 14, 2023discovered · members disagree
notification delay · 381 days
Mar 29, 2024first filing
Apr 11, 2024most 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. FEB 20Leak sitebianlian postfirst filing · attacker claim · unverifiedday 0
  2. MAR 29IN AGIN AG noticestates nationwide total 211,650+38d
  3. MAR 29DE AGDE AG noticeno count stated+38d
  4. APR 1IL AGIL AG noticeno count stated+41d
  5. APR 2CA AGCA AG noticeno count stated+42d
  6. APR 2MT AGMT AG notice132 MT residents+42d
  7. APR 2WA AGWA AG notice18,757 WA residents+42d
  8. APR 2ME AGME AG noticestates nationwide total 211,650+42d
  9. APR 3NH AGNH AG notice87 NH residents+43d
  10. APR 3SC AGSC AG notice19,974 SC residents+43d
  11. APR 3MA AGMA AG notice312 MA residents+43d
  12. APR 6Leak sitebianlian postattacker claim · unverified+46d
  13. APR 11OR AGOR AG noticemost recent · no count stated+51d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 21, 2024
IN AG
Discovered
Mar 14, 2023MT AG + SC AGFeb 20, 2024DE AG + IL AG + CA AG +2Mar 14, 2024ME AG + OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
DE AG + CA AG + MT AG +5
Attack vector
Third-Party / Supply Chain
DE 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)

211,650

Sum of filed state slices

39,918· 18.9% of stated

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

US211,650
SC19,974
WA18,757
IN587
MA312
MT132
NH87
ME69

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing11 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

51 days

Cadence

~1 / 3.9d

vs. multi-state median

6.4× 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.