Confirmed breach. Intrusion Oct 13, 2024, discovered Oct 23, 2024 — the first regulatory filing landed 385 days later (flagged late). 8,042 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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
8,042
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 13, 2024
When the intrusion reportedly occurred, per the linked filings
American Associated Pharmacies reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-13 and was reported on 2025-11-12. 28 Indiana residents were affected. 8,042 individuals affected in total.
Affected (this filing): 8,042
Leak >180d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
American Associated Pharmacies notified the New Hampshire Attorney General on November 17, 2025, regarding a cybersecurity incident detected on October 23, 2024. The incident involved unauthorized access starting October 13, 2024, resulting in system encryption (ransomware) and data exfiltration. 11 New Hampshire residents were affected, with their names potentially exposed. The company engaged forensic investigators, law enforcement, and offered 12 months of credit monitoring.
Affected (this filing): 11
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.