Confirmed breach. Intrusion Feb 7, 2025, discovered Mar 7, 2025 — the first regulatory filing landed 24 days later. 1,678 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 clocksMaine✓ ME AG ≤30d · 25dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
1,678
Data types
1
PII
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 7, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Mar 7, 2025
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Workers Federal Credit Union reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-07 and was reported on 2025-03-31. 1 Indiana residents were affected. 1,678 individuals affected in total.
Workers Federal Credit Union, a financial services organization based in Littleton, MA, experienced an inadvertent disclosure on February 7, 2025. The breach was discovered on March 7, 2025. A total of 1,678 individuals were affected, including 16 Maine residents. Written notification was sent to affected individuals on March 31, 2025. Identity theft protection services were offered for 24 months.
Affected (this filing): 16
ME AG ≤30d · 25d
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.