DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddan0nhigh sensitivity
Merged incident · 6 filings

S&F Concrete Contractors — May 2024 breach

Clustered 6 filings across 5 jurisdictions · filing window May 23, 2024 → Aug 8, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

1,013

First → last filing

May 23, 2024 → Aug 8, 2024

Merge confidence

100%

incident inc_121854e67aca4d57 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion May 5, 2024–May 20, 2024, discovered May 20, 2024 — the first regulatory filing landed 79 days later. 1,013 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 77-day schedule across 4 filings beginning May 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
79days

Discovered → first regulatory filing

Leak precedence
76days 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
77days

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.

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

Sensitive data

identity_government

Incident timeline

May 5, 2024breach begins
May 20, 2024discovered
notification delay · 79 days
Aug 7, 2024first filing
Aug 8, 2024most recent filing

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

Member cascade — every filing about this breach

  1. MAY 23Leak sitedan0n postfirst filing · attacker claim · unverifiedday 0
  2. MAY 23Leak sitedan0n postattacker claim · unverifiedday 0
  3. AUG 7VT AGVT AG noticeno count stated+76d
  4. AUG 7NH AGNH AG notice72 NH residents+76d
  5. AUG 7ME AGME AG noticestates nationwide total 1,013+76d
  6. AUG 8MA AGMA AG noticemost recent · 841 MA residents+77d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 5, 2024 – May 20, 2024
VT AG
Discovered
May 20, 2024· 15d undetected
ME AG
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID
VT AG + NH AG + ME AG +1
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)

1,013

Sum of filed state slices

921· 90.9% of stated

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

US1,013
MA841
NH72
ME8

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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 23, 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

77 days

Cadence

~1 / 15.4d

vs. multi-state median

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