DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilincritical sensitivity
Merged incident · 10 records

CornerStone Staffing Solutions, Inc. — November 2025 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Sep 11, 2026 → Sep 18, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

366,122

First → last dated filing

Sep 11, 2026 → Sep 18, 2026

Merge confidence

100%

incident inc_f2a2796fa17845eb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Nov 6, 2025–Nov 21, 2025, discovered Nov 17, 2025. 366,122 individuals reported across the linked filings. Data reported: Government ID, Minor, Financial account, and 6 more. Notifications rolled out on a 7-day schedule across 8 dated filings beginning Sep 11, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
263days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 298dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_governmentminor

Incident timeline

Nov 6, 2025breach begins
Nov 17, 2025discovered · members disagree
Sep 11, 2026first dated filing
Sep 18, 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 and leak-site claim in this incident

  1. NOV 13Leak siteqilin postfirst record · attacker claim · unverifiedday 0
  2. SEP 1MA AGMA AG noticefiling day not on record · 243 MA residents—
  3. SEP 11IA AGIA AG notice915 IA residents+302d
  4. SEP 11WA AGWA AG notice681 WA residents+302d
  5. SEP 11IN AGIN AG noticestates nationwide total 366,122+302d
  6. SEP 11CA AGCA AG noticeno count stated+302d
  7. SEP 11OR AGOR AG noticestates nationwide total 366,122+302d
  8. SEP 12VT AGVT AG notice7 VT residents+303d
  9. SEP 15TX AGTX AG noticestates nationwide total 366,122+306d
  10. SEP 18NH AGNH AG noticemost recent · 45 NH residents+309d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 6, 2025 – Nov 21, 2025
MA AG
Discovered
Nov 17, 2025MA AG + IA AG + WA AG +2Apr 15, 2026OR AGAug 7, 2026TX AGfilings disagree on discovery
Data types
Authentication · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
MA AG + WA AG + VT AG +4
Attack vector
Unauthorized Access
IA 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)

366,122

Sum of filed state slices

6,486· 1.8% of stated

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

US366,122
TX4,425
IA915
WA681
MA243
IN170
NH45
VT7

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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
Reviewed
operator-reviewed Sep 16, 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

7 days

Cadence

~1 / 1d

vs. multi-state median

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