Clustered 3 filings across 2 jurisdictions · filing window Nov 5, 2024 → Jun 25, 2025. View entity profile → Other incidents for this victim →
incident inc_76b0490384364447 · merge_method human · 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.
PII · Government ID
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 5, 2024 → Nov 10, 2024
When the intrusion reportedly occurred, per the linked filings
Bluegrass helps leading brands and flavor houses concept, test an d produce the custom flavors and formulations they need to stay a head. We are ready to upload more than 45 GB of private corporate docum ents including: NDAs, SSNs, financial data (audits, payment detai ls, reports), contact numbers and e-mail addresses of employees e tc.
Bluegrass helps leading brands and flavor houses concept, test an d produce the custom flavors and formulations they need to stay a head. We are ready to upload more than 45 GB of private corporate docum ents including: NDAs, SSNs, financial data (audits, payment detai ls, reports), contact numbers and e-mail addresses of employees e tc.
Jun 6, 2025
Reported by MAINE AG filing
Between November 5–10, 2024, an unauthorized external actor gained access to Bluegrass Ingredients, Inc.'s network and copied certain files. The breach was discovered on June 6, 2025 after a comprehensive review of impacted files. Affected data includes names and Social Security numbers. Three Maine residents were affected out of 2,166 total. Bluegrass notified federal law enforcement, provided credit monitoring via Experian (12 months), and enhanced security protocols.
Affected (this filing): 3
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.