Kayser-Roth, Inc. — February 2016 breach

Clustered 7 filings across 6 jurisdictions · filing window Jun 19, 2017 → Aug 9, 2017. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

90,548

First → last filing

Jun 19, 2017 → Aug 9, 2017

Merge confidence

100%

incident inc_7d104b776e00495c · merged by deterministic · confidence 100%

Part of the Aptos supply-chain incident (2017) — at least 12 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe a third-party compromise. Intrusion Feb 1, 2016–Aug 9, 2017, discovered Feb 6, 2017 — the first regulatory filing landed 133 days later (flagged late). 90,548 individuals reported across the linked filings. Data reported: PII, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 51-day schedule across 7 filings beginning Jun 19, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

133days

Discovered → first regulatory filing

Discovery variance

227days

Range of discovered_at dates across filings

Filing span

51days

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 >45dSouth Carolina✓ SC CRA notice dueFull 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.