Detroit PBS reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-12 and was reported on 2025-02-21. 2 Indiana residents were affected. 1,694 individuals affected in total.
Affected (this filing): 1,694
Clustered 2 filings across 2 jurisdictions · filed Feb 21, 2025. View entity profile → Other incidents for this victim →
incident inc_253d11c22e744406 · 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.
Identity (basic) · Government ID · Financial account
IN MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 12, 2024
When the intrusion reportedly occurred, per the linked filings
Sep 1, 2024
Reported by MARYLAND AG filing
Detroit PBS reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-12 and was reported on 2025-02-21. 2 Indiana residents were affected. 1,694 individuals affected in total.
Affected (this filing): 1,694
Detroit PBS notified Maryland AG of a ransomware incident affecting 17 Maryland residents. Unauthorized actor gained access Aug 12-31, 2024, encrypting files and exfiltrating data including names, SSNs, and financial account info. Incident detected Sept 1, 2024. Detroit PBS engaged in investigation, secured environment, and offered credit monitoring.
Affected (this filing): 17
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.