Confirmed breach. Intrusion Jan 2, 2023–Jul 26, 2023, discovered Aug 31, 2023 — the first regulatory filing landed 15 days later. 1 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 ≤30d · 15dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME NH
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 2, 2023 → Jul 26, 2023
When the intrusion reportedly occurred, per the linked filings
241 days
Breach discovered
Aug 31, 2023
Reported by MAINE AG filing
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Intuit Inc. notified New Hampshire residents that unauthorized parties accessed TurboTax accounts using credentials obtained from a non-Intuit source. Intuit secured accounts and offered one year of Experian identity protection services. Data potentially exposed included prior year tax returns or current returns in progress.
Intuit Inc. reported an account takeover (ATO) incident affecting one Maine resident. The breach occurred between January 2 and July 26, 2023, and was discovered on August 31, 2023. The compromised data included the individual's name and driver's license number. Intuit provided written notification to the affected person on September 15, 2023, and offered a 12-month membership to Experian IdentityWorks for identity theft protection.
Affected (this filing): 1
ME AG ≤30d · 15d
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.