DisclosureLens
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedavoslockerhigh sensitivity
Merged incident · 6 records

Coghlin Electrical Contractors — July 2021 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window Sep 30, 2021 → Oct 10, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

2,040

First → last dated filing

Sep 30, 2021 → Oct 10, 2021

Merge confidence

100%

incident inc_3fef34be94e84650 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 16, 2021–Jul 20, 2021, discovered Jul 20, 2021. 2,040 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 10-day schedule across 4 dated filings beginning Sep 30, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
10days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 82dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 16, 2021breach begins
Jul 20, 2021discovered
Sep 30, 2021first dated filing
Oct 10, 2021most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. AUG 28Leak siteavoslocker postfirst record · attacker claim · unverifiedday 0
  3. SEP 30IN AGIN AG noticestates nationwide total 2,040+33d
  4. OCT 5MA AGMA AG notice1,004 MA residents+38d
  5. OCT 8NH AGNH AG noticestates nationwide total 2,040+41d
  6. OCT 10ME AGME AG noticemost recent · states nationwide total 2,040+43d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 16, 2021
IN AG
Discovered
Jul 20, 2021· 4d undetected
IL AG + NH AG + ME AG
Data types
Financial account · Identity (basic) · Government ID
MA AG + NH AG + ME AG
Attack vector
Unauthorized Access
NH AG

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)

2,040

Sum of filed state slices

1,093· 53.6% of stated

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

US2,040
MA1,004
NH53
ME31
IN5

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 filing5 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

10 days

Cadence

~1 / 3.3d

vs. multi-state median

1.7× 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.