GLOBALClaimed by BianLianFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Feb 20, 2024bd_2460fbf06e71ff54
On Q Financial is a Mortgage Company specializing in new home financing and existing home refinancing.
Clustered 5 filings across 4 jurisdictions · filing window Feb 20, 2024 → Apr 11, 2024. View entity profile → Other incidents for this victim →
incident inc_823b0b4dd0a4403e · 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.
MT OR WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 20, 2024
When the intrusion reportedly occurred, per the linked filings
On Q Financial is a Mortgage Company specializing in new home financing and existing home refinancing.
Feb 28, 2024
Reported by WASHINGTON AG filing
Mar 14, 2024
Reported by OREGON AG filing
On Q Financial, a finance sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2024-02-28 and filed notice on 2024-04-02. 18,757 Washington residents were affected. 34 days elapsed between awareness and notification. 7 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 18,757
Q Financial, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-04-02. The breach occurred on 2/20/2024. 132 Montana residents were affected.
Affected (this filing): 132
On Q Financial is a Mortgage Company specializing in new home financing and existing home refinancing.
On Q Financial, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2024-04-11. The breach occurred during 2/20/2024. The breach was discovered on 3/14/2024. Notice was sent on 3/29/2024.
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.