GLOBALClaimed by QilinFirst sightinglinked via multi-signal match · 100%
Posted to leak site Feb 19, 2025bd_1c93af73e2ded0be
Gaines County Courthouse 101 South Main Mailing Address: P.O. Box 847 Seminole, Texas 79360 (432) 758-5411
Clustered 3 filings across 2 jurisdictions · filing window Feb 19, 2025 → May 22, 2025. View entity profile → Other incidents for this victim →
incident inc_0317d4d3bb03494c · 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 · Government ID
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 19, 2025
When the intrusion reportedly occurred, per the linked filings
Gaines County Courthouse 101 South Main Mailing Address: P.O. Box 847 Seminole, Texas 79360 (432) 758-5411
Gaines County Courthouse 101 South Main Mailing Address: P.O. Box 847 Seminole, Texas 79360 (432) 758-5411
Apr 14, 2025
Reported by MAINE AG filing
On February 19, 2025, Gaines County, Texas experienced a network disruption in which an unauthorized actor may have acquired personal information including names, dates of birth, and Social Security numbers. Discovery of data involvement was completed on April 14, 2025. One Maine resident was notified on May 20, 2025, out of 3,160 total individuals affected. The County offered 12 months of IDX identity protection services and implemented additional technical 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): 1