Clustered 3 filings across 1 jurisdiction · filing window Jun 1, 2026 → Jul 1, 2026. View entity profile → Other incidents for this victim →
incident inc_8a734ac3aca641d9 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
Identity (basic) · Government ID · Financial account
MA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 9, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 9, 2026
Reported by MASSACHUSETTS AG filing
Wells Fargo Bank, N.A. reported that on January 9, 2026, checks and deposit slips containing customer personal information (name, address, bank account numbers, and potentially SSN/DOB) were stolen from a Philadelphia branch. The bank is offering two years of Experian IdentityWorks and monitoring services. No specific count of affected individuals was disclosed in this notice.
Wells Fargo Bank, N.A. filed a notification with the Massachusetts Attorney General's office on January 13, 2026, regarding a cybersecurity incident affecting customer data. The notification encloses an Experian IdentityWorks credit monitoring subscription for affected individuals. The document provides guidance on protecting accounts, including monitoring statements, changing passwords, and placing credit freezes. Specific details regarding the nature of the breach, the number of affected individuals, or the cause are not explicitly detailed in this notification letter.
Wells Fargo Bank, N.A. filed a notification with the Massachusetts Attorney General's office on January 13, 2026, regarding a cybersecurity incident affecting customer data. The notification includes an offer for Experian IdentityWorks credit monitoring services, indicating the exposure of personal identifiers such as Social Security Numbers and dates of birth. The specific nature of the breach and the number of affected individuals are not detailed in this notification letter.
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.