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

Krispy Kreme Doughnut Corporation — November 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Jun 1, 2025 → Jun 18, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

161,676

First → last filing

Jun 1, 2025 → Jun 18, 2025

Merge confidence

100%

incident inc_405396600f784732 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Nov 19, 2024–Dec 23, 2024, discovered Nov 29, 2024 — the first regulatory filing landed 184 days later (flagged late). 161,676 individuals reported across the linked filings. Data reported: Government ID, Authentication, Financial account, and 4 more. Notifications rolled out on a 17-day schedule across 11 filings beginning Jun 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
184days

Discovered → first regulatory filing

Discovery variance
174days

Range of discovered_at dates across filings

Filing span
17days

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 clocksVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 27dSouth Carolina✓ SC CRA notice dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Nov 19, 2024breach begins
Nov 29, 2024discovered · members disagree
notification delay · 184 days
Jun 1, 2025first filing
Jun 18, 2025most 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 16DE AGDE AG noticeno count stated+15d
  3. JUN 16IN AGIN AG noticestates nationwide total 161,676+15d
  4. JUN 16VT AGVT AG noticeno count stated+15d
  5. JUN 17CA AGCA AG noticeno count stated+16d
  6. JUN 17RI AGRI AG notice125 RI residents+16d
  7. JUN 17MA AGMA AG notice179 MA residents+16d
  8. JUN 18ME AGME AG noticestates nationwide total 161,676+17d
  9. JUN 18NH AGNH AG notice12 NH residents+17d
  10. JUN 18SC AGSC AG notice7,266 SC residents+17d
  11. JUN 18TX AGTX AG noticemost recent · states nationwide total 161,676+17d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 19, 2024
IN AG
Discovered
Nov 29, 2024IL AG + DE AG + VT AG +4May 22, 2025ME AG + TX AGfilings disagree on discovery
Data types
Authentication · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + RI AG + MA AG +7
Attack vector
Unauthorized Access
DE 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)

161,676

Sum of filed state slices

19,361· 12.0% of stated

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

US161,676
SC7,266
TX6,948
IN4,810
MA179
RI125
ME21
NH12

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

17 days

Cadence

~1 / 1.7d

vs. multi-state median

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