Manduka — February 2017 breach

Clustered 7 filings across 5 jurisdictions · filing window Mar 26, 2018 → Aug 1, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

64,270

First → last filing

Mar 26, 2018 → Aug 1, 2018

Merge confidence

100%

incident inc_489bd6cb9c894e89 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe a ransomware attack. Intrusion Feb 22, 2017–Jul 6, 2018, discovered Feb 25, 2018 — the first regulatory filing landed 29 days later. 64,270 individuals reported across the linked filings. Data reported: PCI, PII, Financial credentials, and 2 more. Notifications rolled out on a 128-day schedule across 7 filings beginning Mar 26, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

29days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

128days

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 ≤45dCalifornia✓ CA 60-day OK · 29dFull 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.