DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed21 filings · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 21 filings

VeriSource Services, Inc. — February 2024 breach

Clustered 21 filings across 14 jurisdictions · filing window May 4, 2024 → Apr 28, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

21 filings

States

14

Affected · reported

4,052,972

First → last dated filing

May 4, 2024 → Apr 28, 2025

Merge confidence

100%

incident inc_a43f06ae128547a3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 21 regulatory filings. Intrusion Feb 27, 2024–Feb 28, 2024, discovered Feb 27, 2024 — the first regulatory filing landed 67 days later; 6 later filings were flagged late. 4,052,972 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 359-day schedule across 18 dated filings beginning May 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
67days

Discovered → first regulatory filing

Discovery variance
415days

Range of discovered_at dates across filings

Filing span
359days

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 · 174dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMaine✓ ME AG ≤30d · 11dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 27, 2024breach begins
Feb 27, 2024discovered · members disagree
notification delay · 67 days
May 4, 2024first dated filing
Apr 28, 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. MAY 4ME AGME AG noticefirst filing · states nationwide total 1,382day 0
  2. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  3. AUG 20IN AGIN AG noticestates nationwide total 115,256+108d
  4. AUG 20CA AGCA AG noticeno count stated+108d
  5. AUG 20NH AGNH AG notice78 NH residents+108d
  6. AUG 20HHS OCRHHS OCR noticestates nationwide total 112,726+108d
  7. AUG 20MT AGMT AG notice59 MT residents+108d
  8. AUG 21VT AGVT AG noticeno count stated+109d
  9. AUG 21MA AGMA AG notice209 MA residents+109d
  10. NOV 1IL AGIL AG noticefiling day not on record · no count stated—
  11. NOV 6NH AGNH AG notice78 NH residents+186d
  12. NOV 6CA AGCA AG noticeno count stated+186d
  13. APR 23DE AGDE AG noticeno count stated+354d
  14. APR 23NE AGNE AG noticefiling day not on record · no count stated—
  15. APR 23VT AGVT AG noticeno count stated+354d
  16. APR 25NH AGNH AG notice3,191 NH residents+356d
  17. APR 25WA AGWA AG notice85,880 WA residents+356d
  18. APR 25ME AGME AG noticestates nationwide total 4,000,000+356d
  19. APR 25CA AGCA AG noticeno count stated+356d
  20. APR 26OR AGOR AG noticestates nationwide total 4,052,972+357d
  21. APR 28SC AGSC AG noticemost recent · 121,108 SC residents+359d
  22. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 27, 2024
ME AG
Discovered
Feb 27, 2024IL AGFeb 28, 2024CA AG + NH AG + MT AG +5Apr 23, 2024ME AGApr 17, 2025ME AG + OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PII
ME AG + CA AG + NH AG +9
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)

4,052,972

Sum of filed state slices

214,463· 5.3% of stated

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

US4,052,972
SC121,108
WA85,880
NH3,191
ME3,163
IN853
MA209
MT59

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

359 days

Cadence

~1 / 21.1d

vs. multi-state median

59.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.