DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressHHS OCRState AGConfirmed13 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakiracritical sensitivity
Merged incident · 13 records

Paylogix — November 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

11

Affected · reported

1,249,201

First → last dated filing

Aug 14, 2026 → Sep 18, 2026

Merge confidence

100%

incident inc_27d82f500e5e40ea · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings, 1 press report and 1 unverified claim. Intrusion Nov 13, 2025–Nov 18, 2025, discovered Nov 1, 2025. 1,249,201 individuals reported across the linked filings. Data reported: Biometric, Government ID, Financial account, and 7 more. Notifications rolled out on a 35-day schedule across 9 dated filings beginning Aug 14, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
261days

Range of discovered_at dates across filings

Filing span
35days

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 >180dOregon✗ OR AG >45dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

biometricfinancial_credentialsidentity_government

Incident timeline

Nov 13, 2025breach begins
Nov 1, 2025discovered · members disagree
Aug 14, 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. JAN 15Leak siteakira postfirst record · attacker claim · unverifiedday 0
  2. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  3. AUG 1MA AGMA AG noticefiling day not on record · 6,420 MA residents—
  4. AUG 14VT AGVT AG notice1,102 VT residents+211d
  5. AUG 14OR AGOR AG noticestates nationwide total 1,249,201+211d
  6. AUG 14CA AGCA AG noticeno count stated+211d
  7. AUG 14WA AGWA AG notice28,449 WA residents+211d
  8. AUG 14DE AGDE AG noticeno count stated+211d
  9. AUG 14IN AGIN AG notice15,027 IN residents+211d
  10. AUG 14NH AGNH AG notice2,304 NH residents+211d
  11. AUG 17SC AGSC AG noticeno count stated+214d
  12. SEP 18HHS OCRHHS OCR noticemost recent · states nationwide total 41,739+246d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 13, 2025 – Nov 18, 2025
OR AG
Discovered
Nov 1, 2025NH AGNov 18, 2025OR AG + WA AGJul 20, 2026IL AGfilings disagree on discovery
Data types
Biometric · Employment · Financial · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + CA AG +6
Attack vector
Ransomware
WA 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)

1,249,201

Sum of filed state slices

53,302· 4.3% of stated

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

US1,249,201
WA28,449
IN15,027
MA6,420
NH2,304
VT1,102

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

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing11 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 21, 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

35 days

Cadence

~1 / 4.4d

vs. multi-state median

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