FabFitFun — April 2020 breach

Clustered 9 filings across 9 jurisdictions · filing window Sep 15, 2020 → Sep 28, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

209,984

First → last filing

Sep 15, 2020 → Sep 28, 2020

Merge confidence

100%

incident inc_7d9e0a5317aa4e4c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe hacking. Intrusion Apr 26, 2020–Aug 3, 2020, discovered May 14, 2020 — the first regulatory filing landed 124 days later (flagged late). 209,984 individuals reported across the linked filings. Data reported: PII, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 13-day schedule across 9 filings beginning Sep 15, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

124days

Discovered → first regulatory filing

Discovery variance

99days

Range of discovered_at dates across filings

Filing span

13days

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 clocksCalifornia✗ CA 60-day late · 81dMaine⏱ ME AG >30d · 42dOregon✓ OR AG ≤45dWashington✓ WA AG ≤30dFull 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.