Clustered 2 filings across 2 jurisdictions · filing window Jun 5, 2026 → Jun 9, 2026. View entity profile → Other incidents for this victim →
incident inc_701d147fdeb9400c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · Identity (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 9, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 23, 2026
Reported by MAINE AG, TEXAS AG filings
MasTec, Inc. reported an external system breach (hacking) occurring on August 9, 2025, discovered on April 23, 2026. The incident affected 25,220 individuals, including 11 Maine residents. Notification was sent on June 5, 2026, offering identity theft protection services via CyEx Financial Shield. The breach involved unauthorized access to external systems.
Affected (this filing): 25,220
MasTec, Inc. based in Coral Gables, Florida, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-04-23 and reported on 2026-06-09. 4,827 Texas residents were affected. 25,220 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Financial Information (e.g. account number, credit or debit card number);Date of Birth. Consumers were notified via U.S. Mail.
Affected (this filing): 4,827
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.