Confirmed breach. Intrusion Oct 4, 2024, discovered Jun 26, 2025 — the first regulatory filing landed 5 days later (flagged late). 2 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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2
Data types
—
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 4, 2024
When the intrusion reportedly occurred, per the linked filings
Idealab, a commercial entity, experienced an external system breach (hacking) on October 4, 2024, which was discovered on June 26, 2025. The breach affected 2 Maine residents, who were notified electronically on July 1, 2025. The company offered 24 months of credit and identity monitoring services through IDX.
Affected (this filing): 2
Leak >180dME AG ≤30d · 5d
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.