DisclosureLens
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedstormoushigh sensitivity
Merged incident · 6 filings

SMITH TRANSPORT, LLC — February 2022 breach

Clustered 6 filings across 5 jurisdictions · filing window Mar 14, 2022 May 17, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

10,141

First → last filing

Mar 14, 2022 May 17, 2022

Merge confidence

100%

incident inc_1532ef088c564f9d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Feb 12, 2022, discovered Feb 12, 2022 — the first regulatory filing landed 74 days later. 10,141 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 64-day schedule across 4 filings beginning Mar 14, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
74days

Discovered → first regulatory filing

Discovery variance
59days

Range of discovered_at dates across filings

Leak precedence
44days 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
64days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 12, 2022breach begins
Feb 12, 2022discovered · members disagree
notification delay · 74 days
Apr 27, 2022first filing
May 17, 2022most 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. MAR 14Leak siteragnarlocker postfirst filing · attacker claim · unverifiedday 0
  2. MAR 28Leak sitestormous postattacker claim · unverified+14d
  3. APR 27MA AGMA AG notice49 MA residents+44d
  4. APR 27ME AGME AG noticestates nationwide total 5,921+44d
  5. APR 28NH AGNH AG notice36 NH residents+45d
  6. MAY 17IN AGIN AG noticemost recent · states nationwide total 10,141+64d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2022
ME AG
Discovered
Feb 12, 2022NH AGApr 12, 2022ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
MA AG + ME AG + NH AG
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)

10,141

Sum of filed state slices

922· 9.1% of stated

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

US10,141
IN787
ME50
MA49
NH36

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

64 days

Cadence

~1 / 12.8d

vs. multi-state median

8.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. 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.