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

GSPlatformCo Inc — April 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 11, 2026 → Jan 31, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

537,877

First → last dated filing

Jan 11, 2026 → Jan 31, 2026

Merge confidence

100%

incident inc_e25c35da12234e5b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Apr 1, 2025–Nov 22, 2025, discovered Oct 22, 2025. 537,877 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 20-day schedule across 7 dated filings beginning Jan 11, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
31days

Range of discovered_at dates across filings

Filing span
20days

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 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 51dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 1, 2025breach begins
Oct 22, 2025discovered · members disagree
Jan 11, 2026first dated filing
Jan 31, 2026most 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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 11IN AGIN AG noticefirst filing · states nationwide total 603day 0
  3. JAN 12NH AGNH AG notice66 NH residents+1d
  4. JAN 12CA AGCA AG noticeno count stated+1d
  5. JAN 12WA AGWA AG notice798 WA residents+1d
  6. JAN 12ME AGME AG noticestates nationwide total 537,877+1d
  7. JAN 16VT AGVT AG noticeno count stated+5d
  8. JAN 31OR AGOR AG noticemost recent · states nationwide total 327+20d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2025
IN AG
Discovered
Oct 22, 2025IL AGNov 1, 2025VT AGNov 22, 2025NH AG + WA AG + ME AGfilings disagree on discovery
Data types
Behavior · Identity (basic) · Government ID · Metadata · PII
IL AG + NH AG + CA AG +3
Attack vector
Misconfiguration
NH 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)

537,877

Sum of filed state slices

1,504· 0.3% of stated

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

US537,877
WA798
IN538
ME102
NH66

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 filing8 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 2026 · at least one link edge was human-adjudicated
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

20 days

Cadence

~1 / 3.3d

vs. multi-state median

3.3× 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.