Confirmed breach. Intrusion Mar 30, 2021, discovered Mar 30, 2021 — the first regulatory filing landed 275 days later (flagged late). 17,150 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 clocksMaine✗ ME AG >90d · 275dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
17,150
Data types
—
Jurisdictions
3
AZ ME MT
Linked filings
3
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 30, 2021
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Mar 30, 2021
Reported by MAINE AG filing
275 days
🇺🇸AZHHS OCRFirst filinglinked via same-victim cross-source · 100%
A New Leaf, Inc. reported to HHS on 2021-12-30 a Hacking/IT Incident affecting 10,438 individuals. Breached information located on Network Server. The incident involved a ransomware attack compromising PHI including names, addresses, SSNs, diagnoses, and medications.
Affected (this filing): 10,438
🦞Maine State AGlinked via same-victim cross-source · 100%
A New Leaf, Inc. reported an external system breach (hacking) occurring on March 30, 2021. The incident compromised names and Social Security Numbers of approximately 17,150 individuals, including one Maine resident. The organization notified affected individuals in writing on December 30, 2021, and provided 12 months of credit monitoring through Experian.
Affected (this filing): 17,150
ME AG >90d · 275d
🦬Montana State AGMost recentlinked via same-victim cross-source · 100%
A New Leaf reported a data breach to the Montana Attorney General. The breach was reported on 2021-12-30. The breach occurred on 3/30/2021. 8 Montana residents were affected.
Affected (this filing): 8
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.