Confirmed breach. Intrusion Sep 18, 2024–Sep 19, 2024, discovered Sep 19, 2024 — the first regulatory filing landed 144 days later (flagged late). 49 individuals reported across the linked filings.
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.
Regulatory clocksMaryland✗ MD AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
49
Data types
2
Identity (basic) · PII
Jurisdictions
2
IN MD
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 18, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Sep 19, 2024
Reported by MARYLAND AG filing
144 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Motion Picture Licensing Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-18 and was reported on 2025-02-10. 3 Indiana residents were affected. 49 individuals affected in total.
Motion Picture Licensing Corporation notified Maryland residents of a security incident where an unauthorized party accessed an email account between September 18-19, 2024. The incident involved access to emails and attachments containing names and other personal information. MPLC secured the account, launched an investigation, and implemented additional security measures.
MD AG >90d
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.