DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed14 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

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

9

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

Sensitive data

identity_government

Incident timeline

Feb 16, 2025breach begins
Feb 17, 2025discovered · members disagree
notification delay · 133 days
Jun 30, 2025first dated filing
Sep 4, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUN 30IN AGIN AG noticefirst filing · 482 IN residentsday 0
  2. JUN 30VT AGVT AG noticeno count statedday 0
  3. JUN 30ME AGME AG notice8 ME residentsday 0
  4. JUN 30CA AGCA AG noticeno count statedday 0
  5. JUN 30NE AGNE AG noticefiling day not on record · 12 NE residents—
  6. JUN 30NH AGNH AG notice58 NH residentsday 0
  7. JUN 30MA AGMA AG notice95 MA residentsday 0
  8. JUL 21NH AGNH AG notice62 NH residents+21d
  9. JUL 21ME AGME AG notice13 ME residents+21d
  10. JUL 21CA AGCA AG noticeno count stated+21d
  11. AUG 29ME AGME AG notice15 ME residents+60d
  12. AUG 29CA AGCA AG noticeno count stated+60d
  13. AUG 29MT AGMT AG notice2 MT residents+60d
  14. SEP 4TX AGTX AG noticemost recent · states nationwide total 22,057+66d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 16, 2025
IN AG
Discovered
Feb 17, 2025VT AG + ME AG + CA AG +3Jun 13, 2025ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + ME AG + CA AG +5
Attack vector
Unauthorized Access
VT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

22,057

Sum of filed state slices

1,967· 8.9% of stated

91% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US22,057
TX1,299
IN482
MA95
NH62
ME15
NE12
MT2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing14 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

66 days

Cadence

~1 / 5.5d

vs. multi-state median

11.0× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.