DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
Leak SiteState AGConfirmed3 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 3 filings

Smith Midland Corp — January 2025 breach

Clustered 3 filings across 3 jurisdictions · filing window Feb 3, 2025 → Aug 3, 2026. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Determination

Confirmed

Members

3 filings

States

2

Affected · reported

9

First → last filing

Feb 3, 2025 → Aug 3, 2026

Merge confidence

100%

incident inc_ece7d8abfdc244cf · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records and 1 unverified claim. Intrusion Jan 9, 2025–Jan 15, 2025, discovered Jan 15, 2025 — the first regulatory filing landed 565 days later (flagged late). 9 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
565days

Discovered → first regulatory filing

Leak precedence
545days 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
545days

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 >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 9, 2025breach begins
Jan 15, 2025discovered
notification delay · 565 days
Aug 3, 2026first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. FEB 3Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. AUG 3NH AGNH AG notice2 NH residents+545d
  3. AUG 3MA AGMA AG noticemost recent · 7 MA residents+545d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 9, 2025 – Jan 15, 2025
NH AG
Discovered
Jan 15, 2025· 6d undetected
NH AG
Data types
Identity (basic) · Government ID · Financial account
NH AG + MA AG
Attack vector
Unauthorized Access
NH AG
Response
Notified federal law enforcement · Provided access to credit monitoring services for twelve (12) months, through Experian · Provided impacted individuals with guidance on how to better protect against identity theft and fraud
NH AG

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

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

545 days

Cadence

~1 / 272.5d

vs. multi-state median

109.0× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.