Confirmed breach. Intrusion Mar 12, 2025–May 5, 2025, discovered May 5, 2025 — the first regulatory filing landed 46 days later. 199,506 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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
199,506
Data types
2
Identity (basic) · Credentials
Jurisdictions
2
CA IN
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 12, 2025
When the intrusion reportedly occurred, per the linked filings
54 days
Breach discoveredletter-grounded
May 5, 2025
Reported by CALIFORNIA AG filing
46 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
The Mindfuel Foundation reported a data breach to the Indiana Attorney General. The breach occurred on 2025-03-12 and was reported on 2025-06-20. 1,510 Indiana residents were affected. 199,506 individuals affected in total.
The Mindfuel Foundation disclosed that a snapshot of a historical testing database, potentially containing limited production data (names, emails, phone numbers, usernames, hashed passwords) from before May 2021, was placed in a location accessible to developers by a third-party service provider and may have been viewed by web crawlers on May 5, 2025. The organization removed the data, reset affected passwords, and implemented new secure file transfer and legacy account removal processes.
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.