Rialto Markets LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-21. The breach occurred from 11/30/2021 to 2/25/2022. 23 Montana residents were affected.
Affected (this filing): 23
Clustered 2 filings across 2 jurisdictions · filed Apr 21, 2022. View entity profile → Other incidents for this victim →
incident inc_bba3cc63f6524d01 · 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
Nov 30, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 29, 2022
Reported by MAINE AG filing
Rialto Markets LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-21. The breach occurred from 11/30/2021 to 2/25/2022. 23 Montana residents were affected.
Affected (this filing): 23
Rialto Markets LLC reported a data breach impacting 4,427 individuals, which was discovered on March 29, 2022, after occurring on November 30, 2021. The breach resulted from an external system hack. The compromised data included names combined with financial account or credit/debit card numbers along with their associated security codes or PINs. Affected individuals were notified on April 21, 2022, and offered 24 months of identity monitoring services through Kroll.
Affected (this filing): 4,427
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.