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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
—
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
MA
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Salem Five Bank disclosed a security incident on June 2, 2026, where customer personal information (name, address, DOB, SSN) was inadvertently disclosed to another party. The bank investigated internally, offered two years of free credit monitoring, and notified affected customers via letter dated June 3, 2026. Risk of fraud is assessed as low.
Breach window
Jun 2, 2026
When the intrusion reportedly occurred, per the linked filings
Salem Five Bank notified Massachusetts customers of a security incident on July 10, 2026, where personal information (name, address, DOB, SSN, account number) was inadvertently disclosed to another party. The bank investigated internally, offered two years of credit monitoring, and advised customers to monitor accounts and place fraud alerts.
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.