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

PurFoods Holdings, LLC — January 2023 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

1,289,643

First → last filing

Jan 1, 2023 → Aug 31, 2023

Merge confidence

100%

incident inc_934d354da28a4cfa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Jan 16, 2023–Feb 22, 2023, discovered Feb 22, 2023. 1,289,643 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 242-day schedule across 13 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
138days

Range of discovered_at dates across filings

Filing span
242days

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 clocksWashington✗ WA AG >90dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dMaine⏱ ME AG >30d · 46dSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 16, 2023breach begins
Feb 22, 2023discovered · members disagree
Jan 1, 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 31SC AGSC AG notice17,660 SC residents+211d
  3. AUG 25ME AGME AG noticestates nationwide total 1,237,681+236d
  4. AUG 25NH AGNH AG notice1,297 NH residents+236d
  5. AUG 25HHS OCRHHS OCR noticestates nationwide total 1,289,643+236d
  6. AUG 25MA AGMA AG notice11,793 MA residents+236d
  7. AUG 25WA AGWA AG notice9,094 WA residents+236d
  8. AUG 25MT AGMT AG notice3,192 MT residents+236d
  9. AUG 25CA AGCA AG noticeno count stated+236d
  10. AUG 25IN AGIN AG noticestates nationwide total 1,237,681+236d
  11. AUG 25VT AGVT AG noticeno count stated+236d
  12. AUG 25SC AGSC AG notice43,819 SC residents+236d
  13. AUG 31OR AGOR AG noticemost recent · states nationwide total 1,237,681+242d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 16, 2023 – Feb 22, 2023
SC AG
Discovered
Feb 22, 2023IL AG + SC AG + NH AG +4Jul 10, 2023ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
SC AG + ME AG + NH AG +6
Attack vector
Ransomware
SC 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,289,643

Sum of filed state slices

120,035· 9.3% of stated

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

US1,289,643
IN48,592
SC43,819
MA11,793
WA9,094
MT3,192
ME2,248
NH1,297

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

242 days

Cadence

~1 / 20.2d

vs. multi-state median

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