Confirmed breach. Intrusion Sep 14, 2023, discovered Oct 23, 2023 — the first regulatory filing landed 11 days later. 1,380 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 clocksHIPAA✓ HHS notifiedMaine✓ ME AG ≤30d · 11dFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
1,380
Data types
2
Identity (basic) · Financial account
Jurisdictions
2
ME MN
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 14, 2023
When the intrusion reportedly occurred, per the linked filings
39 days
Breach discovered
Oct 23, 2023
Reported by MAINE AG filing
🇺🇸MNHHS OCRFirst filinglinked via same-victim cross-source · 100%
WACOSA reported to HHS on 2023-11-03 a Hacking/IT Incident affecting 1380 individuals. Breached information located on Network Server. The incident involved PHI including names, addresses, DOB, SSNs, financial info, and diagnoses. The CE implemented additional administrative and technical safeguards.
Affected (this filing): 1,380
HHS notified
🦞Maine State AGMost recentlinked via same-victim cross-source · 100%
WACOSA, a non-profit organization, experienced an external system breach on September 14, 2023, which was discovered on October 23, 2023. The breach compromised the names and financial account numbers or credit/debit card numbers (with security codes) of 2,064 individuals, including 2 Maine residents. Notification to affected consumers was sent on November 3, 2023, and 12 months of identity theft protection services were offered.
Affected (this filing): 2
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.