Clustered 4 filings across 4 jurisdictions · filing window Aug 26, 2019 → Oct 10, 2019. View entity profile → Other incidents for this victim →
incident inc_c871ca25e02c4243 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MD MT WA
HHS OCR · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Mar 11, 2019
When the intrusion reportedly occurred, per the linked filings
Apr 16, 2019
Reported by WASHINGTON AG filing
Calibre CPA Group reported a data breach to the Montana Attorney General. The breach was reported on 2019-08-26. The breach occurred from 3/11/2019 to 5/7/2019. 219 Montana residents were affected.
Affected (this filing): 219
Calibre CPA Group experienced unauthorized access to employee email accounts and a server between March 11, 2019, and May 7, 2019. The incident affected 553 California residents, exposing personal information including names, Social Security numbers, financial account details, driver's license numbers, and medical information. Calibre engaged forensic experts, reset passwords, implemented dual-factor authentication, and provided two years of identity monitoring services through Kroll. The investigation is ongoing, but the incident is considered contained.
Affected (this filing): 553
Calibre CPA Group reported to HHS on 2019-09-27 a Hacking/IT Incident affecting 7,937 individuals. Breached information located on Email, Network Server. Employees were victims of an email phishing scheme exposing PHI including names and Social Security numbers.
Affected (this filing): 7,937
Calibre CPA Group, a finance sector entity reported a unclear/unknown incident to the Washington Attorney General. The organization became aware of the incident on 2019-04-16 and filed notice on 2019-10-10. 983 Washington residents were affected. 177 days elapsed between awareness and notification. 36 days to identify the breach. 21 days to contain the breach.
Affected (this filing): 983
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.