GLOBALClaimed by Hunters InternationalFirst sightinglinked via shared-victim match · 100%
Posted to leak site Oct 7, 2024bd_f5f8d504fe5bbd31
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Clustered 4 filings across 3 jurisdictions · filing window Oct 7, 2024 → Jul 1, 2025. View entity profile → Other incidents for this victim →
incident inc_25dfbdbb51cc4085 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
CA IN
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 4, 2024 → Oct 7, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 7, 2024
Reported by CALIFORNIA AG filing
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Idealab, a technology incubator, notified the California AG of a data breach where an unknown actor acquired data without authorization between Oct 4-7, 2024. Idealab became aware of unusual activity on Oct 7, 2024. The incident involved names and potentially SSNs or other government IDs of employees, dependents, and contractors. Idealab engaged cybersecurity experts, secured its network, reported to the FBI, and is offering 24 months of credit monitoring via IDX. The notice was sent on July 1, 2025.
Idealab reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-04 and was reported on 2025-07-01. 4 Indiana residents were affected. 2,790 individuals affected in total.
Affected (this filing):
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.