DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed12 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

YUM! Brands, Inc. — January 2023 breach

Clustered 12 filings across 12 jurisdictions · filing window Jan 1, 2023 → Apr 14, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

300,000

First → last filing

Jan 1, 2023 → Apr 14, 2023

Merge confidence

100%

incident inc_220ef85470464fcb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Jan 4, 2023–Jan 14, 2023, discovered Jan 13, 2023. 300,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 3 more. Notifications rolled out on a 103-day schedule across 12 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
55days

Range of discovered_at dates across filings

Filing span
103days

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.

Regulatory clocksWashington⏱ WA AG >30dMaine✓ ME AG ≤30d · 29dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 4, 2023breach begins
Jan 13, 2023discovered · members disagree
Jan 1, 2023first filing
Apr 14, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 19SEC 8-KSEC 8-K noticeno count stated+18d
  3. APR 7WA AGWA AG notice1,220 WA residents+96d
  4. APR 7ME AGME AG notice11 affected+96d
  5. APR 13CA AGCA AG noticeno count stated+102d
  6. APR 13SC AGSC AG notice3,303 SC residents+102d
  7. APR 13NH AGNH AG notice621 NH residents+102d
  8. APR 14DE AGDE AG noticeno count stated+103d
  9. APR 14MA AGMA AG notice1,602 MA residents+103d
  10. APR 14MT AGMT AG notice58 MT residents+103d
  11. APR 14IN AGIN AG notice15,406 IN residents+103d
  12. APR 14OR AGOR AG noticemost recent · states nationwide total 300,000+103d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 13, 2023 – Jan 14, 2023
WA AG
Discovered
Jan 13, 2023WA AG + SC AG + MT AGMar 9, 2023IL AG + ME AG + OR AGfilings disagree on discovery
Data types
Employment · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + SC AG + NH AG +5
Attack vector
Ransomware
SEC 8-K

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)

300,000

Sum of filed state slices

22,221· 7.4% of stated

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

US300,000
IN15,406
SC3,303
MA1,602
WA1,220
NH621
MT58
ME11

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

103 days

Cadence

~1 / 9.4d

vs. multi-state median

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