Confirmed breach. Intrusion Mar 12, 2022–Mar 14, 2022, discovered Jan 13, 2023 — the first regulatory filing landed 62 days later. 1,876 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine⏱ ME AG >30d · 62dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1,876
Data types
2
Government ID · Identity (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 12, 2022 → Mar 14, 2022
When the intrusion reportedly occurred, per the linked filings
Dee Zee, Inc. reported a ransomware incident occurring March 12-14, 2022, discovered January 13, 2023. The breach affected 1,876 individuals, including one Maine resident. Data compromised included Social Security Numbers. Dee Zee provided 12 months of credit monitoring and identity theft restoration through Experian.
Affected (this filing): 1,876
ME AG >30d · 62dME resident >60d · 62d
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.