Confirmed breach. Intrusion Jul 30, 2024, discovered Jul 1, 2024 — the first regulatory filing landed 241 days later (flagged late). 10,958 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 clocksMaryland✗ MD AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
10,958
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
2
IN MD
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discovered
Jul 1, 2024
Reported by MARYLAND AG filing
Breach window
Jul 30, 2024
When the intrusion reportedly occurred, per the linked filings
212 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Northwest Arkansas Community College reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-30 and was reported on 2025-02-27. 16 Indiana residents were affected. 10,958 individuals affected in total.
Northwest Arkansas Community College (NWACC) experienced a ransomware attack in July 2024. The incident resulted in the potential exfiltration of personal information, including names, addresses, SSNs, driver's license numbers, government IDs, financial account information, and dates of birth. NWACC notified law enforcement, engaged cybersecurity specialists, and implemented remediation measures including global password resets and endpoint detection. 27 Maryland residents were notified and offered 12 months of credit monitoring.
Affected (this filing): 27
MD AG >90d
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.