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

THE HONEY BAKED HAM COMPANY LLC — December 2020 breach

Clustered 7 filings across 7 jurisdictions · filing window Jan 26, 2021 → Feb 6, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

141,837

First → last dated filing

Jan 26, 2021 → Feb 6, 2021

Merge confidence

100%

incident inc_d70bb362025f4422 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe a ransomware attack. Intrusion Dec 13, 2020, discovered Dec 13, 2020. 141,837 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 11-day schedule across 6 dated filings beginning Jan 26, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
29days

Range of discovered_at dates across filings

Filing span
11days

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 clocksDelaware✓ DE credit monitoring dueSouth Carolina✓ SC CRA notice dueMaine✓ ME AG ≤30d · 25dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 13, 2020breach begins
Dec 13, 2020discovered · members disagree
Jan 26, 2021first dated filing
Feb 6, 2021most 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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 26MT AGMT AG noticefirst filing · 3 MT residentsday 0
  3. JAN 27DE AGDE AG noticestates nationwide total 141,837+1d
  4. JAN 29IN AGIN AG noticestates nationwide total 141,837+3d
  5. FEB 2SC AGSC AG notice4,708 SC residents+7d
  6. FEB 5ME AGME AG noticestates nationwide total 141,837+10d
  7. FEB 6MA AGMA AG noticemost recent · 1,229 MA residents+11d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 13, 2020
MT AG
Discovered
Dec 13, 2020IL AG + MT AG + SC AGJan 11, 2021DE AG + ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MT AG + DE AG + SC AG +2
Attack vector
Ransomware
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)

141,837

Sum of filed state slices

6,363· 4.5% of stated

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

US141,837
SC4,708
MA1,229
IN393
ME23
DE7
MT3

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 filing7 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
Reviewed
operator-reviewed Jun 12, 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

11 days

Cadence

~1 / 2.2d

vs. multi-state median

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