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

Complete Payroll Solutions — February 2024 breach

Clustered 12 filings across 9 jurisdictions · filing window Oct 23, 2024 → Jun 5, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

405,094

First → last dated filing

Oct 23, 2024 → Jun 5, 2025

Merge confidence

100%

incident inc_3b41b8e690af4263 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Feb 21, 2024–Mar 10, 2024, discovered Mar 10, 2024 — the first regulatory filing landed 227 days later; 2 later filings were flagged late. 405,094 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 225-day schedule across 10 dated filings beginning Oct 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
227days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
225days

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 bdayLeak gap✗ Leak >180dRhode Island✗ RI AG >45dMaine⏱ ME AG >30d · 227dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 21, 2024breach begins
Mar 10, 2024discovered
notification delay · 227 days
Oct 23, 2024first dated filing
Jun 5, 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. OCT 23ME AGME AG noticefirst filing · states nationwide total 320day 0
  2. APR 25VT AGVT AG noticeno count stated+184d
  3. APR 25MT AGMT AG notice40 MT residents+184d
  4. APR 25CA AGCA AG noticeno count stated+184d
  5. APR 25IN AGIN AG noticestates nationwide total 405,094+184d
  6. APR 25NH AGNH AG notice21,963 NH residents+184d
  7. APR 25NE AGNE AG noticefiling day not on record · 41 NE residents—
  8. APR 29RI AGRI AG notice28,184 RI residents+188d
  9. MAY 1IL AGIL AG noticefiling day not on record · no count stated—
  10. MAY 9CA AGCA AG noticeno count stated+198d
  11. MAY 28NH AGNH AG notice22,033 NH residents+217d
  12. JUN 5RI AGRI AG noticemost recent · 29,734 RI residents+225d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 21, 2024
ME AG
Discovered
Mar 10, 2024· 18d undetected
ME AG + VT AG + MT AG +5
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + VT AG + MT AG +5
Attack vector
Unauthorized Access
ME 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)

405,094

Sum of filed state slices

53,395· 13.2% of stated

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

US405,094
RI29,734
NH22,033
IN1,539
NE41
MT40
ME8

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

225 days

Cadence

~1 / 25d

vs. multi-state median

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