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

PEPSI BOTTLING VENTURES LLC — December 2022 breach

Clustered 11 filings across 8 jurisdictions · filing window Feb 10, 2023 → Jun 28, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

28,050

First → last filing

Feb 10, 2023 → Jun 28, 2023

Merge confidence

100%

incident inc_5b4014bb0bcc4660 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Dec 23, 2022–Jan 19, 2023, discovered Jan 10, 2023 — the first regulatory filing landed 31 days later; 1 later filing was flagged late. 28,050 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 7 more. Notifications rolled out on a 138-day schedule across 11 filings beginning Feb 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
138days

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 clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 41dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 23, 2022breach begins
Jan 10, 2023discovered
notification delay · 31 days
Feb 10, 2023first filing
Jun 28, 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. FEB 10MT AGMT AG noticefirst filing · 7 MT residentsday 0
  2. FEB 10DE AGDE AG noticeno count statedday 0
  3. FEB 10MA AGMA AG notice28 MA residentsday 0
  4. FEB 10VT AGVT AG noticeno count statedday 0
  5. FEB 10IN AGIN AG noticestates nationwide total 28,050day 0
  6. FEB 10MT AGMT AG notice7 MT residentsday 0
  7. FEB 10SC AGSC AG notice1,048 SC residentsday 0
  8. FEB 20ME AGME AG noticestates nationwide total 17,612+10d
  9. JUN 28NH AGNH AG notice7 NH residents+138d
  10. JUN 28VT AGVT AG noticeno count stated+138d
  11. JUN 28ME AGME AG noticemost recent · states nationwide total 28,050+138d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 23, 2022 – Jan 19, 2023
MT AG
Discovered
Jan 10, 2023· 18d undetected
MT AG + DE AG + VT AG +3
Data types
Credentials · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + DE AG + VT AG +4
Attack vector
Ransomware
MT 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)

28,050

Sum of filed state slices

1,124· 4.0% of stated

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

US28,050
SC1,048
IN29
MA28
MT7
NH7
ME5

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 statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

138 days

Cadence

~1 / 13.8d

vs. multi-state median

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