TrueFire — August 2019 breach

Clustered 4 filings across 4 jurisdictions · filing window Feb 13, 2020 → Mar 10, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

8,190

First → last filing

Feb 13, 2020 → Mar 10, 2020

Merge confidence

100%

incident inc_072277730c7f48ec · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes unauthorized access. Intrusion Aug 3, 2019–Jan 14, 2020, discovered Jan 10, 2020 — the first regulatory filing landed 34 days later. 8,190 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Authentication, and 1 more. Notifications rolled out on a 26-day schedule across 4 filings beginning Feb 13, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

34days

Discovered → first regulatory filing

Filing span

26days

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.

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.