DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

YELLOW CORPORATION — March 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Jun 26, 2026 → Jul 8, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

258,781

First → last dated filing

Jun 26, 2026 → Jul 8, 2026

Merge confidence

100%

incident inc_b916aecc46a845ee · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Mar 22, 2025–Mar 27, 2025, discovered Mar 27, 2025. 258,781 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 12-day schedule across 7 dated filings beginning Jun 26, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
230days

Range of discovered_at dates across filings

Filing span
12days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMassachusetts✗ MA AG >90dCalifornia✗ CA 60-day late · 456dTexas✗ TX AG >30dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 22, 2025breach begins
Mar 27, 2025discovered · members disagree
Jun 26, 2026first dated filing
Jul 8, 2026most 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 about this breach

  1. JUN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUN 26MA AGMA AG noticefirst filing · 491 MA residentsday 0
  3. JUN 26IN AGIN AG notice6,191 IN residentsday 0
  4. JUN 26NE AGNE AG noticefiling day not on record · no count stated—
  5. JUN 26CA AGCA AG noticeno count statedday 0
  6. JUN 26SC AGSC AG noticeno count statedday 0
  7. JUN 26NH AGNH AG noticeno count statedday 0
  8. JUN 30TX AGTX AG noticestates nationwide total 258,781+4d
  9. JUL 8OR AGOR AG noticemost recent · states nationwide total 258,498+12d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 27, 2025
MA AG
Discovered
Mar 27, 2025MA AG + NE AG + CA AG +3Nov 12, 2025IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
IL AG + MA AG + NE AG +4
Attack vector
Unauthorized Access
MA 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)

258,781

Sum of filed state slices

19,865· 7.7% of stated

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

US258,781
TX13,183
IN6,191
MA491

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 claim

No leak-site claim on record for this incident.

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

12 days

Cadence

~1 / 2d

vs. multi-state median

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