Alpha Baking Co Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-22 and was reported on 2025-06-13. 4,442 Indiana residents were affected. 21,463 individuals affected in total.
Affected (this filing): 21,463
Clustered 2 filings across 2 jurisdictions · filed Jun 13, 2025. View entity profile → Other incidents for this victim →
incident inc_80340483eee246c8 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
PII
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 22, 2025
When the intrusion reportedly occurred, per the linked filings
May 22, 2025
Reported by MAINE AG filing
Alpha Baking Co Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-22 and was reported on 2025-06-13. 4,442 Indiana residents were affected. 21,463 individuals affected in total.
Affected (this filing): 21,463
Alpha Baking Co., Inc. reported an external system breach (hacking) in which an unauthorized third party obtained files stored on the company network. Unusual activity was identified on January 23, 2025; a forensic review was completed on May 2, 2025. The breach affected 21,463 individuals total and 1 Maine resident. Affected data included personal information. Kroll 12-month identity monitoring services were offered to affected individuals.
Affected (this filing): 1
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.