Burdette, Smith, & Bish — March 2017 breach

Clustered 5 filings across 3 jurisdictions · filing window Jun 26, 2017 → Jul 14, 2017. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

14,185

First → last filing

Jun 26, 2017 → Jul 14, 2017

Merge confidence

100%

incident inc_d4a6e9f2ddc54c85 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a ransomware attack. Intrusion Mar 23, 2017–Apr 12, 2017, discovered Apr 2, 2017 — the first regulatory filing landed 85 days later (flagged late). 14,185 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 2 more. Notifications rolled out on a 18-day schedule across 5 filings beginning Jun 26, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

85days

Discovered → first regulatory filing

Discovery variance

10days

Range of discovered_at dates across filings

Filing span

18days

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.

Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.