Clustered 3 filings across 3 jurisdictions · filing window Dec 8, 2023 → Jan 16, 2024. View entity profile → Other incidents for this victim →
incident inc_77225548c0b94503 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR WA
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 1, 2023 → Oct 8, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 7, 2023
Reported by CALIFORNIA AG, WASHINGTON AG filings
Oct 11, 2023
Reported by OREGON AG filing
McCarthy & Holthus reported a data breach to the Oregon Attorney General. The breach was reported on 2023-12-08. The breach occurred during 10/1/2023 - 10/8/2023. The breach was discovered on 10/11/2023. 2,365 individuals were affected. Notice was sent on 12/6/2023.
Affected (this filing): 2,365
McCarthy & Holthus, LLP and its affiliate Quality Loan Service Corporation experienced unauthorized access to their network between October 1 and October 8, 2023. The incident was discovered on October 7, 2023. Affected data includes names, Social Security numbers, loan numbers, and other personal information. The company engaged third-party forensics, notified law enforcement, and is offering 24 months of credit monitoring.
McCarthy & Holthus LLP, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-10-07 and filed notice on 2024-01-16. 700 Washington residents were affected. 101 days elapsed between awareness and notification. 6 days to identify the breach. 1 days to contain the breach.
Affected (this filing): 700
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.