GLOBALClaimed by PlayFirst sightinglinked via multi-signal match · 100%
Posted to leak site Jun 13, 2024bd_78b90e7d8b6e5b04
United States
Clustered 3 filings across 3 jurisdictions · filing window Jun 13, 2024 → Sep 3, 2024. View entity profile → Other incidents for this victim →
incident inc_e1c41df45a904f7a · 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.
PII · Identity (basic) · Government ID
IN ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
United States
Jun 24, 2024 → Jun 25, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2024
Reported by MAINE AG filing
Elyria Foundry Holdings LLC detected suspicious activity on June 25, 2024, determining that an unknown actor accessed its network for several hours between June 24–25, 2024, and may have viewed or copied files containing employee, spouse, and dependent name and Social Security number data. The review was completed August 1, 2024. One Maine resident was affected. Affected individuals were offered 12-month credit monitoring through Cyberscout.
Elyria Foundry Holdings LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-24 and was reported on 2024-09-03. 5 Indiana residents were affected. 2,193 individuals affected in total.
Affected (this filing):
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): 1