Clustered 3 filings across 3 jurisdictions · filing window Jul 7, 2024 → Mar 19, 2025. View entity profile → Other incidents for this victim →
incident inc_eb0dca2419d24381 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN MD
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 11, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 20, 2024
Reported by MARYLAND AG filing
Strauss Brands (founded in 1937) supplies distributors, restaurants, retailers, and hotels with premium quality, ethically rais ed specialty meats. Products include american grass-fed beef, american lamb, and raised veal. The total amount of data leakage is 264.4 GB
Strauss Brands LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-11 and was reported on 2025-03-19. 8 Indiana residents were affected. 4,336 individuals affected in total.
Strauss Brands LLC notified the Maryland AG of a data security incident affecting 9 Maryland residents. Unauthorized access occurred between June 11-20, 2024. Impacted data included names, SSNs, driver's licenses, financial account numbers, and medical/health insurance information. Strauss engaged law enforcement and third-party specialists, implemented technical safeguards, and offered 12 months of credit monitoring.
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.
Affected (this filing): 4,336
Affected (this filing): 9