Urban Resource Institute reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-20. The breach occurred on 7/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Oct 20, 2021 → Oct 21, 2021. View entity profile → Other incidents for this victim →
incident inc_a865493d14c64fdf · 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
Jul 23, 2020
When the intrusion reportedly occurred, per the linked filings
Jun 26, 2021
Reported by MAINE AG filing
Urban Resource Institute reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-20. The breach occurred on 7/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Urban Resource Institute, a New York-based non-profit, reported an external system breach (hacking) occurring on May 20, 2020, discovered on June 26, 2021. The incident compromised the names and financial account numbers (including credit/debit card numbers with security codes/PINs) of approximately 16,000 individuals, including 6 Maine residents. The organization provided written notification on October 20, 2021, and offered 12 months of identity theft protection services through IDX.
Affected (this filing): 16,003
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.