All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed9 filings · 8 statesUnverified claimConfirmedEnforcedcl0phigh sensitivity

Merged incident · 9 filings

MASTEC, INC. — August 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Oct 31, 2025 → Jun 9, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

25,220

First → last filing

Oct 31, 2025 → Jun 9, 2026

Merge confidence

100%

incident inc_d27493c7b8704576 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 1, 2025–Aug 31, 2025, discovered Oct 1, 2025 — the first regulatory filing landed 246 days later (flagged late). 25,220 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 220-day schedule across 8 filings beginning Oct 31, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

246days

Discovered → first regulatory filing

Discovery variance

204days

Range of discovered_at dates across filings

Leak precedence

215days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

220days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMassachusetts✗ MA AG >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Aug 1, 2025breach begins

Oct 1, 2025discovered · members disagree

notification delay · 246 days

Jun 4, 2026first filing

Jun 9, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

OCT 31Leak sitecl0p postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
JUN 4NH AGNH AG notice18 NH residents+215d
JUN 5IN AGIN AG noticestates nationwide total 25,220auto-linked+216d
JUN 5NE AGNE AG noticeno count statedauto-linked+216d
JUN 5VT AGVT AG notice8 VT residentsauto-linked+216d
JUN 5ME AGME AG noticestates nationwide total 25,220auto-linked+216d
JUN 5SC AGSC AG noticeno count statedauto-linked+216d
JUN 9TX AGTX AG noticestates nationwide total 25,220auto-linked+220d
JUN 9MA AGMA AG noticemost recent · 142 MA residentsauto-linked+220d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 1, 2025 – Aug 31, 2025
Discovered: Oct 1, 2025NH AG + NE AG + SC AG +1Apr 23, 2026ME AG + TX AGfilings disagree on discovery
Data types: Credentials · Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

25,220

Sum of filed state slices

5,060· 20.1% of stated

80% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US25,220

TX4,827

MA142

IN54

NH18

ME11

VT8

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 22, 2026 · at least one link edge was human-adjudicated
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

220 days

Cadence

~1 / 27.5d

vs. multi-state median

27.5× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.