Clustered 3 filings across 1 jurisdiction · filing window Jun 1, 2026 → Jul 1, 2026. View entity profile → Other incidents for this victim →
incident inc_684225c8b42947dc · merge_method llm · confidence 100%
Time between earliest and latest filing
Not recorded for this incident
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.
Financial account · PII
MA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Fall River Municipal Credit Union notified members on June 9, 2026, that Visa USA Fraud Control reported unauthorized access to a third-party data center processing POS/ATM transactions. The incident compromised Visa debit card information. The Credit Union issued new card numbers and disconnected old ones. No fraud was detected, but members were advised to monitor accounts and place security freezes.
Fall River Municipal Credit Union notified members on July 14, 2026, that Visa USA Fraud Control reported unauthorized access to a third-party data center processing POS/ATM transactions. The incident compromised Visa debit card information. The Credit Union issued new card numbers and disconnected old ones, but stated personal information was not believed to be used for fraud.
Fall River Municipal Credit Union notified members on July 28, 2026, that Visa USA Fraud Control reported unauthorized access to a third-party data center processing POS/ATM transactions. The incident compromised Visa debit card information. The Credit Union proactively reissued new card numbers and disconnected old ones, though no fraud was detected.
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.