DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed12 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

Jackson Lewis — January 2022 breach

Clustered 12 filings across 7 jurisdictions · filing window Jan 20, 2023 → Aug 31, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

7

Affected · reported

20,647

First → last filing

Jan 20, 2023 → Aug 31, 2023

Merge confidence

100%

incident inc_1bc0fd142c35464d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Jan 7, 2022, discovered Aug 16, 2022 — the first regulatory filing landed 157 days later (flagged late). 20,647 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 223-day schedule across 12 filings beginning Jan 20, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
157days

Discovered → first regulatory filing

Discovery variance
175days

Range of discovered_at dates across filings

Filing span
223days

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 · 126dMaine⏱ ME AG >30d · 37dVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 7, 2022breach begins
Aug 16, 2022discovered · members disagree
notification delay · 157 days
Jan 20, 2023first filing
Aug 31, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 20MA AGMA AG noticefirst filing · 2,301 MA residentsday 0
  2. JAN 20CA AGCA AG noticeno count statedday 0
  3. JAN 20IN AGIN AG noticestates nationwide total 20,647day 0
  4. JAN 20MT AGMT AG notice202 MT residentsday 0
  5. JAN 25NH AGNH AG notice3 NH residents+5d
  6. FEB 17CA AGCA AG noticeno count stated+28d
  7. FEB 17HHS OCRHHS OCR noticestates nationwide total 986+28d
  8. MAR 16CA AGCA AG noticeno count stated+55d
  9. MAR 16ME AGME AG noticestates nationwide total 20,647+55d
  10. MAR 16VT AGVT AG noticeno count stated+55d
  11. MAR 20NH AGNH AG notice59 NH residents+59d
  12. AUG 31CA AGCA AG noticemost recent · no count stated+223d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 7, 2022
CA AG
Discovered
Aug 16, 2022CA AG + MT AG + NH AGFeb 7, 2023ME AG + VT AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
MA AG + MT AG + NH AG +4
Attack vector
Unauthorized Access
MT 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)

20,647

Sum of filed state slices

2,757· 13.4% of stated

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

US20,647
MA2,301
MT202
IN178
NH59
ME17

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

223 days

Cadence

~1 / 20.3d

vs. multi-state median

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