TABB Inc. — August 2024 breach

Clustered 11 filings across 9 jurisdictions · filing window Feb 12, 2026 → Mar 2, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

Affected · reported

5,309

First → last filing

Feb 12, 2026 → Mar 2, 2026

Merge confidence

100%

incident inc_f203a18320f4404c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a misconfiguration. Intrusion Aug 14, 2024, discovered Aug 14, 2024 — the first regulatory filing landed 547 days later (flagged late). 5,309 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 18-day schedule across 11 filings beginning Feb 12, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

547days

Discovered → first regulatory filing

Discovery variance

72days

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 clocksMaine✗ ME AG >90d · 475dOregon✗ OR AG >45dIowa✓ IA AG ≤5 bdayFull 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.