DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed9 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhunters_internationalhigh sensitivity
Merged incident · 9 records

InterCon Construction, Inc. — November 2024 breach

Clustered 9 records across 8 jurisdictions: 8 filings and 1 leak-site claim · filed Jan 30, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 records

States

8

Affected · reported

6,634

First → last dated filing

Jan 30, 2025

Merge confidence

100%

incident inc_0c89e04c32394a31 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 9, 2024–Nov 20, 2024, discovered Nov 9, 2024. 6,634 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
10days

Range of discovered_at dates across filings

Filing span
0days

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 clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 72dLeak gap⏱ Leak >30dMaryland⏱ MD AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 9, 2024breach begins
Nov 9, 2024discovered · members disagree
Jan 30, 2025first dated filing
—watching for filings

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. NOV 19Leak sitehunters_international postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 30ME AGME AG noticestates nationwide total 6,634+72d
  4. JAN 30IN AGIN AG noticestates nationwide total 6,634+72d
  5. JAN 30MD AGMD AG notice8 MD residents+72d
  6. JAN 30NH AGNH AG notice2 NH residents+72d
  7. JAN 30VT AGVT AG noticeno count stated+72d
  8. JAN 30NE AGNE AG noticefiling day not on record · 48 NE residents—
  9. JAN 30MA AGMA AG noticemost recent · 1 MA residents+72d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 9, 2024 – Nov 20, 2024
ME AG
Discovered
Nov 9, 2024IL AGNov 19, 2024ME AG + MD AG + NH AG +2filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
ME AG + MD AG + NH AG +3
Attack vector
Unauthorized Access
ME 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)

6,634

Sum of filed state slices

135· 2.0% of stated

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

US6,634
IN75
NE48
MD8
NH2
ME1
MA1

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 25, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.