Confirmed breach. Intrusion Jan 15, 2025, discovered Jan 15, 2025 — the first regulatory filing landed 29 days later. 1,061 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 >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1,061
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
2
IN MD
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 15, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jan 15, 2025
Reported by MARYLAND AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Perfect Plastic Printing Corp reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-15 and was reported on 2025-02-13. 5 Indiana residents were affected. 1,061 individuals affected in total.
Perfect Plastic Printing Corp. notified the Maryland Attorney General of a data event affecting one Maryland resident. An unknown actor accessed systems on Jan 15, 2025, copying files containing names, SSNs, and financial account info. PPP notified law enforcement, provided 12 months of Equifax credit monitoring, and is implementing additional security safeguards.
Affected (this filing): 1
MD AG >30d
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.