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

Marten Transport — September 2021 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Mar 25, 2022 → Mar 29, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

35,294

First → last dated filing

Mar 25, 2022 → Mar 29, 2022

Merge confidence

100%

incident inc_cb7db35be4134f4e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 30, 2021–Oct 4, 2021, discovered Oct 3, 2021. 35,294 individuals reported across the linked filings. Data reported: Government ID, Minor, Authentication, and 7 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
156days

Range of discovered_at dates across filings

Filing span
4days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 156dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_governmentminor

Incident timeline

Sep 30, 2021breach begins
Oct 3, 2021discovered · members disagree
Mar 25, 2022first dated filing
Mar 29, 2022most recent dated filing

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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 25Leak sitehive postfirst record · attacker claim · unverifiedday 0
  3. MAR 25WA AGWA AG notice521 WA residents+59d
  4. MAR 25MA AGMA AG notice92 MA residents+59d
  5. MAR 25IN AGIN AG noticestates nationwide total 35,294+59d
  6. MAR 25OR AGOR AG noticestates nationwide total 35,294+59d
  7. MAR 25ME AGME AG noticestates nationwide total 35,294+59d
  8. MAR 25CA AGCA AG noticeno count stated+59d
  9. MAR 25MT AGMT AG notice17 MT residents+59d
  10. MAR 29NH AGNH AG noticemost recent · 31 NH residents+63d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 30, 2021 – Oct 4, 2021
WA AG
Discovered
Oct 3, 2021IL AG + WA AG + CA AG +2Mar 8, 2022ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
WA AG + MA AG + ME AG +3
Attack vector
Unauthorized Access
WA 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)

35,294

Sum of filed state slices

1,693· 4.8% of stated

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

US35,294
IN1,024
WA521
MA92
NH31
MT17
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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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

4 days

Cadence

~1 / 0.6d

vs. multi-state median

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