DisclosureLens
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

BIMBO BAKERIES USA, INC. — August 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 31, 2026 → Sep 4, 2026 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

46,064

First → last dated filing

Aug 31, 2026 → Sep 4, 2026

Merge confidence

100%

incident inc_8ebaffe27e654443 · merged by deterministic · confidence 100%

Part of the ORACLE CORPORATION supply-chain incident (2025) — at least 8 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a third-party compromise. Intrusion Aug 9, 2025, discovered Oct 6, 2025 — the first regulatory filing landed 329 days later; 2 later filings were flagged late. 46,064 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
329days

Discovered → first regulatory filing

Discovery variance
317days

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 leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dWashington✗ WA AG >90dCalifornia✓ CA AG copy ≤15d · 4dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 9, 2025breach begins
Oct 6, 2025discovered · members disagree
notification delay · 329 days
Aug 31, 2026first dated filing
Sep 4, 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. AUG 31IN AGIN AG noticefirst filing · states nationwide total 46,064day 0
  2. SEP 1MA AGMA AG noticefiling day not on record · 363 MA residents—
  3. SEP 4CA AGCA AG noticeno count stated+4d
  4. SEP 4OR AGOR AG noticestates nationwide total 46,064+4d
  5. SEP 4WA AGWA AG notice786 WA residents+4d
  6. SEP 4TX AGTX AG noticestates nationwide total 46,064+4d
  7. SEP 4NH AGNH AG notice94 NH residents+4d
  8. SEP 4VT AGVT AG noticemost recent · 53 VT residents+4d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 9, 2025
IN AG
Discovered
Oct 6, 2025WA AG + NH AGDec 6, 2025OR AGAug 19, 2026TX AGfilings disagree on discovery
Data types
Employment · Financial account · Identity (basic) · Government ID · PCI
MA AG + WA AG + TX AG +3
Attack vector
Third-Party / Supply Chain
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)

46,064

Sum of filed state slices

6,082· 13.2% of stated

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

US46,064
TX3,982
IN804
WA786
MA363
NH94
VT53

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

4 days

Cadence

~1 / 0.7d

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.