DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed6 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Merged incident · 6 filings

CORPORATION SERVICE COMPANY — August 2025 breach

Clustered 6 filings across 6 jurisdictions · filing window Aug 1, 2026 → Aug 14, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

3,065

First → last filing

Aug 1, 2026 → Aug 14, 2026

Merge confidence

100%

incident inc_93613df46ad64b15 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Aug 10, 2025–Aug 25, 2025, discovered Aug 10, 2025 — the first regulatory filing landed 356 days later (flagged late). 3,065 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 13-day schedule across 6 filings beginning Aug 1, 2026. Each member filing remains the legal record for its jurisdiction.

What the filings say

TX AG

Corporation Service Company based in Wilmington, Delaware, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-07-15 and reported on 2026-08-14. 2,481 Texas residents were affected. 20,283 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Date of Birth. Consumers were notified via U.S. Mail.

AI-generated summary of the linked filing — not the filing's own words, and not independently verified.

Litigation Timing

Supplemental
Notification delay
356days

Discovered → first regulatory filing

Discovery variance
339days

Range of discovered_at dates across filings

Filing span
13days

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 · 368dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Incident timeline

Aug 10, 2025breach begins
Aug 10, 2025discovered · members disagree
notification delay · 356 days
Aug 1, 2026first filing
Aug 14, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 13NH AGNH AG notice61 NH residents+12d
  3. AUG 13CA AGCA AG noticeno count stated+12d
  4. AUG 13MA AGMA AG notice500 MA residents+12d
  5. AUG 13VT AGVT AG notice23 VT residents+12d
  6. AUG 14TX AGTX AG noticemost recent · 2,481 affected+13d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 10, 2025 – Aug 25, 2025
NH AG
Discovered
Aug 10, 2025NH AG + CA AGJul 15, 2026IL AG + TX AGfilings disagree on discovery
Data types
Government ID · Identity (basic) · Financial account
IL AG + NH AG + CA AG +3
Attack vector
Unauthorized Access
NH AG
Response
Launched an investigation, with the assistance of third-party forensic specialists · Engaged a third party to conduct a comprehensive and time-consuming review of the information at risk · Providing access to credit monitoring services for twelve (12) months, through TransUnion
NH AG

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

Affected residents by state

per-state reported counts

TX2,481
MA500
NH61
VT23

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing6 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

13 days

Cadence

~1 / 2.6d

vs. multi-state median

1.6× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.

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.