OuterBox LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-09-03 and was reported on 2026-04-08. 1 Indiana residents were affected. 323 individuals affected in total.
Affected (this filing): 323
Clustered 2 filings across 2 jurisdictions · filed Apr 8, 2026. View entity profile → Other incidents for this victim →
incident inc_2032616182cb4ea6 · merge_method human · 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 TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 3, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 15, 2026
Reported by TEXAS AG filing
OuterBox LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-09-03 and was reported on 2026-04-08. 1 Indiana residents were affected. 323 individuals affected in total.
Affected (this filing): 323
OuterBox LLC based in Copley, Ohio, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-03-15 and reported on 2026-04-08. 308 Texas residents were affected. 323 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number). Consumers were notified via U.S. Mail.
Affected (this filing): 308
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.