Confirmed breach. Intrusion Feb 17, 2025–Feb 19, 2025, discovered Feb 17, 2025 — the first regulatory filing landed 45 days later. 225 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — 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 claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
225
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
1
ID
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 17, 2025 → Feb 19, 2025
When the intrusion reportedly occurred, per the linked filings
Idaho Transportation Department reported a cybersecurity incident involving a single email account compromised between Feb 17-19, 2025. Unauthorized access exposed PII (names, addresses, SSNs) of 225 Idaho residents. The department secured the account, notified the Idaho AG, and is offering one year of credit monitoring via Experian.
Affected (this filing): 225
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.