AIS InfoSource — February 2025 breach

Clustered 14 filings across 9 jurisdictions · filing window Jun 30, 2025 → Sep 4, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

Affected · reported

22,057

First → last dated filing

Jun 30, 2025 → Sep 4, 2025

Merge confidence

100%

incident inc_d4c9e308254c40b5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. The filings describe unauthorized access. Intrusion Feb 16, 2025–Feb 21, 2025, discovered Feb 17, 2025 — the first regulatory filing landed 133 days later (flagged late); 3 later filings were also flagged late. 22,057 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 66-day schedule across 13 dated filings beginning Jun 30, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

133days

Discovered → first regulatory filing

Discovery variance

116days

Range of discovered_at dates across filings

Filing span

66days

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 clocksVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 116dTexas✗ TX AG >30dMaine⏱ ME AG >30d · 46dMassachusetts✓ MA credit monitoring dueFull 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.