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

Southeast Series of Lockton Companies, LLC (Lockton) — November 2024 breach

Clustered 24 filings across 17 jurisdictions · filing window Feb 28, 2025 → Jul 1, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

24 filings

States

17

Affected · reported

1,168,911

First → last dated filing

Feb 28, 2025 → Jul 1, 2025

Merge confidence

100%

incident inc_3a7e112f99d84d83 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 24 regulatory filings. The filings describe unauthorized access. Intrusion Nov 20, 2024, discovered Nov 20, 2024 — the first regulatory filing landed 100 days later (flagged late); 3 later filings were also flagged late. 1,168,911 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 4 more. Notifications rolled out on a 123-day schedule across 22 dated filings beginning Feb 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
100days

Discovered → first regulatory filing

Discovery variance
77days

Range of discovered_at dates across filings

Filing span
123days

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 clocksMaryland✗ MD AG >90dWashington✗ WA AG >90dIowa✗ IA AG >5 bdayTexas✗ TX AG >30dHIPAA✓ HHS notifiedMaine✓ ME AG ≤30d · 30dSouth Carolina✓ SC CRA notice dueDelaware✓ DE credit monitoring dueDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 20, 2024breach begins
Nov 20, 2024discovered · members disagree
notification delay · 100 days
Feb 28, 2025first dated filing
Jul 1, 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. FEB 28HHS OCRHHS OCR noticefirst filing · states nationwide total 1,124,727day 0
  2. FEB 28IN AGIN AG noticestates nationwide total 1,168,911day 0
  3. FEB 28MD AGMD AG notice3 MD residentsday 0
  4. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  5. MAR 7ME AGME AG noticestates nationwide total 1,154,625+7d
  6. MAR 7NE AGNE AG noticefiling day not on record · no count stated—
  7. MAR 20MT AGMT AG notice2,528 MT residents+20d
  8. MAR 20VT AGVT AG noticeno count stated+20d
  9. MAR 20WA AGWA AG notice11,907 WA residents+20d
  10. MAR 20SC AGSC AG notice41,422 SC residents+20d
  11. MAR 20DE AGDE AG noticestates nationwide total 982,669+20d
  12. MAR 20CA AGCA AG noticeno count stated+20d
  13. MAR 20OR AGOR AG noticestates nationwide total 112,702+20d
  14. MAR 28IA AGIA AG notice7,597 IA residents+28d
  15. APR 3RI AGRI AG notice3,763 RI residents+34d
  16. APR 8CA AGCA AG noticeno count stated+39d
  17. APR 8NH AGNH AG notice3,248 NH residents+39d
  18. MAY 23DE AGDE AG noticeno count stated+84d
  19. MAY 23NH AGNH AG notice3,268 NH residents+84d
  20. MAY 23CA AGCA AG noticeno count stated+84d
  21. JUN 27NH AGNH AG notice3,270 NH residents+119d
  22. JUN 27DE AGDE AG noticeno count stated+119d
  23. JUN 27CA AGCA AG noticeno count stated+119d
  24. JUL 1TX AGTX AG noticemost recent · states nationwide total 1,168,911+123d
  25. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 20, 2024
IN AG
Discovered
Nov 20, 2024MD AG + IL AG + MT AG +5Feb 5, 2025ME AG + NE AG + DE AG +2filings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MD AG + WA AG +11
Attack vector
Unauthorized Access
HHS OCR

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,168,911

Sum of filed state slices

207,566· 17.8% of stated

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

US1,168,911
TX104,251
SC41,422
IN25,754
WA11,907
IA7,597
RI3,763
ME3,590
DE3,481
NH3,270
MT2,528
MD3

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

123 days

Cadence

~1 / 5.9d

vs. multi-state median

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