TEAM Software — July 2024 breach

Clustered 10 filings across 9 jurisdictions · filing window Oct 24, 2024 → Nov 12, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

99,525

First → last dated filing

Oct 24, 2024 → Nov 12, 2024

Merge confidence

100%

incident inc_47b523462075406b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jul 25, 2024–Jul 26, 2024, discovered Jul 25, 2024 — the first regulatory filing landed 91 days later; 3 later filings were flagged late. 99,525 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 19-day schedule across 9 dated filings beginning Oct 24, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

91days

Discovered → first regulatory filing

Discovery variance

68days

Range of discovered_at dates across filings

Filing span

19days

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 · 90dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMaine⏱ ME AG >30d · 109dMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateFull 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.