Banco Popular de Puerto Rico reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-07. The breach occurred from 5/29/2023 to 5/30/2023. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filing window Aug 7, 2023 → Aug 14, 2023. View entity profile → Other incidents for this victim →
incident inc_3462a68dcd1c474b · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 29, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 24, 2023
Reported by MAINE AG filing
Banco Popular de Puerto Rico reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-07. The breach occurred from 5/29/2023 to 5/30/2023. 5 Montana residents were affected.
Affected (this filing): 5
Banco Popular de Puerto Rico reported a data breach affecting 4 Maine residents, which was discovered on July 24, 2023. The breach occurred on the same day and was attributed to a vendor incident. The compromised information includes names and Social Security Numbers. The bank is offering 24 months of complimentary credit monitoring services through Equifax to the affected individuals.
Affected (this filing): 4
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.