Yellow Corporation and its affiliated debtors and debtors-in-possession under their jointly administered chapter 11 cases (Case No. 23-11069 (Bankr. D. Del. (CTG)) data breach (2026) · DisclosureLens
Yellow Corporation and its affiliated debtors and debtors-in-possession under their jointly administered chapter 11 cases (Case No. 23-11069 (Bankr. D. Del. (CTG))
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✗ CA 60-day late · 456dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
—
Data types
4
Identity (basic) · Government ID · Financial account
Jurisdictions
1
CA
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 27, 2025
When the intrusion reportedly occurred, per the linked filings
Yellow Corporation identified suspicious activity and unauthorized exfiltration of files on March 27, 2025. The incident involved former employee data including names, SSNs, financial account numbers, and medical information. Systems were restored from backups and additional safeguards implemented. No specific count of affected individuals was disclosed.
CA 60-day late · 456dCA AG copy ≤15d · 0d
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.