Confirmed breach. Intrusion Apr 8, 2024, discovered Apr 8, 2024 — the first regulatory filing landed 79 days later (flagged late). 3,389 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 clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3,389
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 8, 2024
When the intrusion reportedly occurred, per the linked filings
Audubon Nature Institute notified consumers on June 26, 2024, of a data breach discovered on April 8, 2024. Unauthorized access resulted in the potential acquisition of full names and Social Security Numbers. The Institute engaged forensic specialists and is offering 12 months of credit monitoring services through TransUnion.
VT AG >45 bdayLeak >30d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Audubon Nature Institute reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-08 and was reported on 2024-06-26. 2 Indiana residents were affected. 3,389 individuals affected in total.
Affected (this filing): 3,389
Leak >30d
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.