GLOBALClaimed by QilinFirst sightinglinked via shared-victim match · 100%
Posted to leak site Jan 19, 2026bd_edd06f07c59276f9
Clustered 4 filings across 3 jurisdictions · filing window Jan 19, 2026 → Apr 28, 2026. View entity profile → Other incidents for this victim →
incident inc_82821bb232d24f74 · merge_method human · 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
CA ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 19, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 3, 2026
Reported by MAINE AG filing
JC Resorts LLC reported to the Maine Attorney General that an external system breach (hacking) occurred on 01/19/2026 and was discovered on 03/03/2026, affecting 5,942 individuals total (1 Maine resident). Written notifications were sent on 04/28/2026 and affected individuals were offered 24 months of Experian credit monitoring and identity restoration services. The Maine AG submission did not enumerate the specific data elements compromised.
JC Resorts LLC notified individuals that on January 19, 2026, an unauthorized actor viewed and copied certain files stored within its computer network. A forensic review identified personal information (categories templated as [Extra1] plus name) belonging to affected individuals. JC Resorts engaged outside cybersecurity specialists, secured the network, notified law enforcement and regulators, and is offering 24 months of Experian IdentityWorks credit monitoring/identity protection. Notification letters were dated April 28, 2026. The total number of affected individuals is not stated in the sample notice.
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): 5,942