GLOBALClaimed by PlayFirst sightinglinked via shared-victim match · 100%
Posted to leak site Jun 6, 2024bd_3ff5cc1b53b2ffec
United States
Clustered 4 filings across 4 jurisdictions · filing window Jun 6, 2024 → Oct 24, 2024. View entity profile → Other incidents for this victim →
incident inc_d07c98e330d24293 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IL MT NH
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 6, 2024
When the intrusion reportedly occurred, per the linked filings
United States
Aug 20, 2024
Reported by NEW HAMPSHIRE AG filing
RRCA Accounts Management Inc. reported to HHS on 2024-10-18 a Hacking/IT Incident affecting 115837 individuals. Breached information located on Desktop Computer, Network Server.
RRCA Accounts Management Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-10-23. The breach occurred on 6/6/2024. 35 Montana residents were affected.
Affected (this filing): 35
RRCA Accounts Management Inc. notified the New Hampshire Attorney General of a ransomware incident involving the 'Play' threat actor. The attack occurred on June 6, 2024, and was discovered on August 20, 2024. The breach potentially impacted the personal information of 7 New Hampshire residents. RRCA provided credit monitoring services and implemented additional security measures.
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.
Affected (this filing): 115,837
Affected (this filing): 7