Millborn Seeds Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-21 and was reported on 2026-05-06. 3 Indiana residents were affected. 123 individuals affected in total.
Affected (this filing): 123
Clustered 2 filings across 2 jurisdictions · filing window May 6, 2026 → May 11, 2026. View entity profile → Other incidents for this victim →
incident inc_9a7f0b80b05749df · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 21, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 28, 2026
Reported by NEW HAMPSHIRE AG filing
Millborn Seeds Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-21 and was reported on 2026-05-06. 3 Indiana residents were affected. 123 individuals affected in total.
Affected (this filing): 123
Millborn Seeds, Inc. notified the New Hampshire Attorney General of a data security incident occurring between January 21 and 28, 2026. The breach affected one New Hampshire resident, exposing name, credit/debit card number, and CVV/expiration date. Millborn engaged forensic experts, implemented security measures, and mailed notification letters offering 12 months of credit monitoring and identity theft recovery services through Kroll.
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.