DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 7 filings

McKim & Creed, Inc. — December 2023 breach

Clustered 7 filings across 6 jurisdictions · filing window Feb 28, 2024 → Jun 6, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

7,079

First → last filing

Feb 28, 2024 → Jun 6, 2024

Merge confidence

100%

incident inc_ae13864070fb4e15 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Dec 15, 2023–Feb 11, 2024, discovered Feb 11, 2024 — the first regulatory filing landed 17 days later (flagged late). 7,079 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 99-day schedule across 5 filings beginning Feb 28, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
17days

Discovered → first regulatory filing

Discovery variance
82days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 15d

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
99days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 34dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2023breach begins
Feb 11, 2024discovered · members disagree
notification delay · 17 days
Feb 28, 2024first filing
Jun 6, 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. FEB 28IN AGIN AG noticefirst filing · states nationwide total 1,376day 0
  2. MAR 13Leak siteransomhub postattacker claim · unverified+15d
  3. MAR 14Leak sitelockbit_3 postattacker claim · unverified+16d
  4. JUN 6VT AGVT AG noticeno count stated+99d
  5. JUN 6MA AGMA AG notice10 MA residents+99d
  6. JUN 6ME AGME AG noticestates nationwide total 7,079+99d
  7. JUN 6MT AGMT AG noticemost recent · 1 MT residents+99d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2023
IN AG
Discovered
Feb 11, 2024VT AG + MT AGMay 3, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + ME AG + MT AG +1
Attack vector
Unauthorized Access
VT 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)

7,079

Sum of filed state slices

32· 0.5% of stated

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

US7,079
IN17
MA10
ME4
MT1

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 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
human
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

99 days

Cadence

~1 / 16.5d

vs. multi-state median

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