Clustered 3 filings across 3 jurisdictions · filing window Oct 11, 2024 → Jan 5, 2026. View entity profile → Other incidents for this victim →
incident inc_d86f391b31e840fc · 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.
MD TX
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Construction Systems inc. provides complete commercial renovation and specialties installation services for medical, commercial office, industrial, retail, education and etc. Construction Systems corporate office is located in 2865 E 14th Ave, Columbus, Ohio, 43219, United States and has 105 employees.The total amount of data leakage is 80.80 GB
Oct 18, 2024
Reported by MARYLAND AG, TEXAS AG filings
Heavy Construction System Specialists, LLC (HCSS) notified the Maryland Attorney General of a ransomware attack detected on October 18, 2024. The incident affected 2 Maryland residents (employees/former employees), exposing names, addresses, phone numbers, employee IDs, and Social Security Numbers. HCSS engaged cybersecurity experts and law enforcement, and offered 24 months of credit monitoring via Experian IdentityWorks.
Heavy Construction Systems Specialists, LLC based in Sugar Land, Texas, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2024-10-18 and reported on 2026-01-05. 882 Texas residents were affected. 1,022 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
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): 2
Affected (this filing): 882