GLOBALClaimed by PlayFirst sightinglinked via multi-signal match · 100%
Posted to leak site Nov 21, 2024bd_728f7ac888b8ab1a
United States
Clustered 2 filings across 2 jurisdictions · filing window Nov 21, 2024 → Dec 11, 2024. View entity profile → Other incidents for this victim →
incident inc_cc537142592644e6 · merge_method deterministic · confidence 62%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance — needs two dated filings.
FEDERAL
Leak Site · SEC 8-K
Earliest sighting first · deep chronology in Litigation Timeline
United States
Nov 29, 2024
Reported by SEC 8-K filing
Dec 11, 2024
Registrant determined the incident material — starts the SEC 4-business-day clock
Krispy Kreme, Inc. (NASDAQ: DNUT) disclosed on Form 8-K Item 1.05 that on November 29, 2024 it was notified of unauthorized activity on a portion of its information technology systems. The company is experiencing operational disruptions, including online ordering in parts of the United States, while shops remain open. Krispy Kreme is working with external cybersecurity experts and has notified federal law enforcement. The incident is reasonably likely to have a material impact on operations and financial condition; cybersecurity insurance is expected to offset some costs.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.