ON Q FINANCIAL, LLC — March 2023 breach
Clustered 13 records across 11 jurisdictions: 11 filings, 1 press report and 1 leak-site claim · filing window Mar 29, 2024 → Apr 11, 2024 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_823b0b4dd0a4403e · merged by human · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
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
- MAR 29IN AGIN AG noticefirst filing · states nationwide total 211,650operator-confirmedday 0
- MAR 29DE AGDE AG noticeno count statedoperator-confirmedday 0
- APR 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- APR 2CA AGCA AG noticeno count statedoperator-confirmed+4d
- APR 2MT AGMT AG notice132 MT residentsoperator-confirmed+4d
- APR 2WA AGWA AG notice18,757 WA residents+4d
- APR 2ME AGME AG noticestates nationwide total 211,650operator-confirmed+4d
- APR 3NH AGNH AG notice87 NH residentsoperator-confirmed+5d
- APR 3SC AGSC AG notice19,974 SC residentsauto-linked+5d
- APR 3MA AGMA AG notice312 MA residentsauto-linked+5d
- APR 6Leak sitebianlian postattacker claim · unverifiedoperator-confirmed+8d
- APR 11OR AGOR AG noticemost recent · no count statedoperator-confirmed+13d
- 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.
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
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.
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
13 days
Cadence
~1 / 1.4d
vs. multi-state median
2.2× 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.