Human Resources, Projects, Documents, and more. If Sunland Asphalt refuses to pay the ransom, every data will be published to the public.
Clustered 3 filings across 3 jurisdictions · filing window Dec 26, 2022 → Mar 20, 2023. View entity profile → Other incidents for this victim →
incident inc_c842a74f9b624c2e · 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.
Government ID · Identity (basic)
ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 27, 2022
When the intrusion reportedly occurred, per the linked filings
Human Resources, Projects, Documents, and more. If Sunland Asphalt refuses to pay the ransom, every data will be published to the public.
Mar 2, 2023
Reported by MAINE AG filing
Sunland Asphalt and Construction, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-20. The breach occurred from 8/27/2022 to 8/29/2022. 4 Montana residents were affected.
Affected (this filing): 4
Sunland Asphalt and Construction, LLC reported an external system breach (hacking) occurring on September 22, 2022, discovered on March 2, 2023. The incident compromised the names and driver's license numbers of 7,884 individuals, including 1 Maine resident. The company provided written notification on March 20, 2023, and offered 24 months of credit monitoring and $1 million in identity theft insurance.
Affected (this filing): 7,884
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.