GLOBALClaimed by PlayFirst sightinglinked via shared-victim match · 100%
Posted to leak site Jun 10, 2024bd_4b98cac8c78be887
United States
Clustered 4 filings across 3 jurisdictions · filing window Jun 10, 2024 → Nov 4, 2024. View entity profile → Other incidents for this victim →
incident inc_56b8b6997b5f4e20 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Government ID · Identity (basic)
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
United States
Jun 11, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 11, 2024
Reported by MAINE AG, NEW HAMPSHIRE AG filings
United States
On June 11, 2024, Belle Tire identified unauthorized activity in its computer systems. A cybercriminal gained access and exfiltrated copies of personal data, including names, addresses, dates of birth, Social Security numbers, and/or driver's license information. The breach affected 29,330 individuals in total, including 4 Maine residents. Belle Tire engaged a third-party forensic team and notified law enforcement. Affected individuals were offered 24 months of Experian IdentityWorks.
Belle Tire notified the NH AG of a data security incident affecting 6 NH residents. The company identified unauthorized system activity on June 11, 2024. A cybercriminal accessed and copied personal data. Belle Tire engaged third-party investigators, contacted law enforcement, and notified residents on Oct 31, 2024, offering credit monitoring.
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): 4
Affected (this filing): 6