Internet Archive reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-17 and was reported on 2025-01-06. 1 Indiana residents were affected. 1,323 individuals affected in total.
Affected (this filing): 1,323
Clustered 2 filings across 2 jurisdictions · filing window Jan 6, 2025 → Jan 23, 2025. View entity profile → Other incidents for this victim →
incident inc_d1511c405f344ea9 · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 17, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 20, 2024
Reported by NEW HAMPSHIRE AG filing
Internet Archive reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-17 and was reported on 2025-01-06. 1 Indiana residents were affected. 1,323 individuals affected in total.
Affected (this filing): 1,323
Internet Archive notified the NH AG of an unauthorized access to its customer service platform between Oct 17-20, 2024, discovered on Oct 20, 2024. The incident affected 4 NH residents, exposing personal information. Internet Archive contained the breach by terminating access and taking the platform offline, notifying affected individuals on Jan 6, 2025.
Affected (this filing): 4
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.